public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>, Jeff Moyer <jmoyer@redhat.com>,
	Jianchao Wang <jianchao.w.wang@oracle.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: fix the cmd_flag_name array
Date: Thu, 24 Jan 2019 08:28:32 -0800	[thread overview]
Message-ID: <1548347312.9266.98.camel@acm.org> (raw)
In-Reply-To: <c3bde1b4-73ea-9120-0e6c-f9f57c0bbb24@kernel.dk>

On Thu, 2019-01-24 at 09:22 -0700, Jens Axboe wrote:
> On 1/24/19 8:09 AM, Jeff Moyer wrote:
> > Jianchao Wang <jianchao.w.wang@oracle.com> writes:
> > 
> > > Swap REQ_NOWAIT and REQ_NOUNMAP and add REQ_HIPRI.
> > > 
> > > Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
> > > ---
> > >  block/blk-mq-debugfs.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/block/blk-mq-debugfs.c b/block/blk-mq-debugfs.c
> > > index 90d6876..f812083 100644
> > > --- a/block/blk-mq-debugfs.c
> > > +++ b/block/blk-mq-debugfs.c
> > > @@ -308,8 +308,9 @@ static const char *const cmd_flag_name[] = {
> > >  	CMD_FLAG_NAME(PREFLUSH),
> > >  	CMD_FLAG_NAME(RAHEAD),
> > >  	CMD_FLAG_NAME(BACKGROUND),
> > > -	CMD_FLAG_NAME(NOUNMAP),
> > >  	CMD_FLAG_NAME(NOWAIT),
> > > +	CMD_FLAG_NAME(NOUNMAP),
> > > +	CMD_FLAG_NAME(HIPRI),
> > >  };
> > >  #undef CMD_FLAG_NAME
> > 
> > Acked-by: Jeff Moyer <jmoyer@redhat.com>
> > 
> > You might consider also adding a comment above the req_flag_bits enum
> > noting that modifications also need to be propagated to cmd_flag_name.
> 
> Agree... These things are notoriously difficult to keep in sync, this
> isn't the first time we've had a fixup. Not sure if that situation
> is improvable, but at least a comment might help.

How about making the build system derive the CMD_FLAG_NAME() declarations
from the include/linux/blk* header files? It's not that hard to do that e.g.
with the help of sed. The output of sed could be written into a .h file and
that file could be #included from blk-mq-debugfs.c.

Bart.

  reply	other threads:[~2019-01-24 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 10:28 [PATCH] blk-mq: fix the cmd_flag_name array Jianchao Wang
2019-01-24 15:09 ` Jeff Moyer
2019-01-24 16:22   ` Jens Axboe
2019-01-24 16:28     ` Bart Van Assche [this message]
2019-01-24 16:34       ` Jens Axboe
2019-01-24 16:21 ` Jens Axboe

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=1548347312.9266.98.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=jianchao.w.wang@oracle.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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