From: ednadolski@gmail.com
To: linux-btrfs@vger.kernel.org
Cc: Edmund Nadolski <enadolski@suse.com>
Subject: [PATCH v2 0/2] Cleanup for some hardcoded constants
Date: Thu, 16 Mar 2017 10:04:32 -0600 [thread overview]
Message-ID: <20170316160434.8126-1-enadolski@suse.com> (raw)
From: Edmund Nadolski <enadolski@suse.com>
This series replaces several hard-coded values with descriptive
symbols.
---
v2:
+ rename SEQ_NONE to SEQ_LAST and move definition to ctree.h
+ clarify comment at __merge_refs()
Edmund Nadolski (2):
btrfs: provide enumeration for __merge_refs mode argument
btrfs: replace hardcoded value with SEQ_LAST macro
fs/btrfs/backref.c | 39 +++++++++++++++++++++------------------
fs/btrfs/ctree.h | 2 ++
fs/btrfs/qgroup.c | 4 ++--
3 files changed, 25 insertions(+), 20 deletions(-)
--
2.10.2
next reply other threads:[~2017-03-16 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 16:04 ednadolski [this message]
2017-03-16 16:04 ` [PATCH v2 1/2] btrfs: provide enumeration for __merge_refs mode argument ednadolski
2017-03-16 16:04 ` [PATCH v2 2/2] btrfs: replace hardcoded value with SEQ_LAST macro ednadolski
2017-03-17 0:56 ` Qu Wenruo
2017-03-28 11:36 ` [PATCH v2 0/2] Cleanup for some hardcoded constants 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=20170316160434.8126-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.