public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: [PATCH 1/4] blkdev: pass gfp_mask and flags to blkdev_issue_flush
Date: Wed, 14 Apr 2010 10:18:54 +0400	[thread overview]
Message-ID: <878w8q5zg1.fsf@openvz.org> (raw)
In-Reply-To: <20100413181023.GB1483@infradead.org> (Christoph Hellwig's message of "Tue, 13 Apr 2010 14:10:23 -0400")

Christoph Hellwig <hch@infradead.org> writes:

>> +enum{
>> +	__BLKDEV_IFL_WAIT,	/* wait for completion */
>> +	__BLKDEV_IFL_BARRIER,	/*issue request with barrier */
>> +};
>> +#define BLKDEV_IFL_WAIT		(1 << __BLKDEV_IFL_WAIT)
>> +#define BLKDEV_IFL_BARRIER	(1 << __BLKDEV_IFL_BARRIER)
>
> This is a very awkward stayle to define flags.  There really should
> be no need for the __-prefixed version.  While you're using them for
> test/set_bit and co there's no reason to use these atomic bitops here.
I need both bit_num(used inside function) and flag (1<<bit_num)
which is used by function caller.
No problem, i'll change it whenever you like
do you like following?
enum{
	IFN_BLKDEV_WAIT,	/* wait for completion */
	IFN_BLKDEV_BARRIER,	/*issue request with barrier */
};
#define BLKDEV_WAIT		(1 << IFN_BLKDEV_WAIT)
#define BLKDEV_BARRIER		(1 << IFN_BLKDEV_BARRIER)

  reply	other threads:[~2010-04-14  6:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 13:03 [PATCH 0/4] blkdev: blkdev_issue_fn cleanups v2 Dmitry Monakhov
2010-04-12 13:03 ` [PATCH 1/4] blkdev: pass gfp_mask and flags to blkdev_issue_flush Dmitry Monakhov
2010-04-12 13:03   ` [PATCH 2/4] blkdev: generalize flags for blkdev_issue_fn functions Dmitry Monakhov
2010-04-12 13:03     ` [PATCH 3/4] blkdev: add blkdev_issue helper functions Dmitry Monakhov
2010-04-12 13:03       ` [PATCH 4/4] patch blk-add-zeroout-helper.patch Dmitry Monakhov
2010-04-13 18:07         ` Christoph Hellwig
2010-04-13 18:06       ` [PATCH 3/4] blkdev: add blkdev_issue helper functions Christoph Hellwig
2010-04-13 18:05     ` [PATCH 2/4] blkdev: generalize flags for blkdev_issue_fn functions Christoph Hellwig
2010-04-13 18:08   ` [PATCH 1/4] blkdev: pass gfp_mask and flags to blkdev_issue_flush Christoph Hellwig
2010-04-13 18:10   ` Christoph Hellwig
2010-04-14  6:18     ` Dmitry Monakhov [this message]
2010-04-26 15:01 ` [PATCH 0/4] blkdev: blkdev_issue_fn cleanups v2 Christoph Hellwig
2010-04-26 17:26   ` Jens Axboe
2010-04-26 17:32     ` Dmitry Monakhov
2010-04-26 17:47       ` Jens Axboe
2010-04-28 13:55     ` [PATCH 0/4] blkdev: blkdev_issue_fn cleanups v3 Dmitry Monakhov
2010-04-28 13:55       ` [PATCH 1/4] blkdev: generalize flags for blkdev_issue_fn functions Dmitry Monakhov
2010-04-28 13:55         ` [PATCH 2/4] blkdev: allow async blkdev_issue_flush requests Dmitry Monakhov
2010-04-28 13:55           ` [PATCH 3/4] blkdev: move blkdev_issue helper functions to separate file Dmitry Monakhov
2010-04-28 13:55             ` [PATCH 4/4] blkdev: add blkdev_issue_zeroout helper function Dmitry Monakhov
2010-04-28 18:17       ` [PATCH 0/4] blkdev: blkdev_issue_fn cleanups v3 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=878w8q5zg1.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --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