From: ednadolski@gmail.com
To: linux-btrfs@vger.kernel.org
Cc: Edmund Nadolski <enadolski@suse.com>
Subject: [PATCH 0/2] Cleanup for some hardcoded constants
Date: Mon, 13 Mar 2017 14:32:02 -0600 [thread overview]
Message-ID: <20170313203204.11857-1-enadolski@suse.com> (raw)
From: Edmund Nadolski <enadolski@suse.com>
This series replaces several hard-coded values with descriptive
symbols.
Edmund Nadolski (2):
btrfs: provide enumeration for __merge_refs mode argument
btrfs: replace hardcoded value with SEQ_NONE macro
fs/btrfs/backref.c | 31 +++++++++++++++++--------------
fs/btrfs/backref.h | 2 ++
fs/btrfs/qgroup.c | 4 ++--
3 files changed, 21 insertions(+), 16 deletions(-)
--
2.10.2
next reply other threads:[~2017-03-13 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 20:32 ednadolski [this message]
2017-03-13 20:32 ` [PATCH 1/2] btrfs: provide enumeration for __merge_refs mode argument ednadolski
2017-03-15 14:47 ` David Sterba
2017-03-13 20:32 ` [PATCH 2/2] btrfs: replace hardcoded value with SEQ_NONE macro ednadolski
2017-03-15 14:38 ` David Sterba
2017-03-16 1:59 ` Qu Wenruo
2017-03-27 18:01 ` David Sterba
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=20170313203204.11857-1-enadolski@suse.com \
--to=ednadolski@gmail.com \
--cc=enadolski@suse.com \
--cc=linux-btrfs@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 NNTP newsgroup(s).