From: Jens Axboe <axboe@kernel.dk>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH] blockdev: convert some macros to static inlines
Date: Thu, 12 Jan 2012 09:16:06 +0100 [thread overview]
Message-ID: <4F0E96C6.9060404@kernel.dk> (raw)
In-Reply-To: <yq1y5tdh8bu.fsf@sermon.lab.mkp.net>
On 01/12/2012 05:07 AM, Martin K. Petersen wrote:
>>>>>> "sfr" == Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
> sfr> We prefer to program in C rather than preprocessor and it fixes
> sfr> this warning when CONFIG_BLK_DEV_INTEGRITY is not set:
>
> I have the patch below in my for-block queue but don't care much either
> way. Jens, which one do you prefer?
I'll take Stephens if you don't mind, I prefer the simplicity of just
typing out the functions.
--
Jens Axboe
next prev parent reply other threads:[~2012-01-12 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 3:42 [PATCH] blockdev: convert some macros to static inlines Stephen Rothwell
2012-01-12 4:07 ` Martin K. Petersen
2012-01-12 8:16 ` Jens Axboe [this message]
2012-01-13 5:41 ` Martin K. Petersen
2012-01-13 7:16 ` 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=4F0E96C6.9060404@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=snitzer@redhat.com \
/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.