From: Daniel Hill <daniel@gluo.nz>
To: linux-bcachefs@vger.kernel.org
Cc: Daniel Hill <daniel@gluo.nz>
Subject: [PATCH 0/1] bcachefs: copygc: remove ambiguity in bucket struct names
Date: Tue, 20 Feb 2024 03:08:41 +1300 [thread overview]
Message-ID: <20240219140857.901012-1-daniel@gluo.nz> (raw)
Having the same variable name for different structures is confusing, lets fix that.
Daniel Hill (1):
bcachefs: copygc: remove ambiguity in bucket struct names
fs/bcachefs/movinggc.c | 40 ++++++++++++++++++++--------------------
1 file changed, 20 insertions(+), 20 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-19 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:08 Daniel Hill [this message]
2024-02-19 14:08 ` [PATCH 1/1] bcachefs: copygc: remove ambiguity in bucket struct names Daniel Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240219140857.901012-1-daniel@gluo.nz \
--to=daniel@gluo.nz \
--cc=linux-bcachefs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).