From: Jens Axboe <axboe@kernel.dk>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: fix an warning of calling blk_rq_aligned()
Date: Thu, 16 Sep 2010 08:23:00 +0200 [thread overview]
Message-ID: <4C91B7C4.6030802@kernel.dk> (raw)
In-Reply-To: <1284609357-3076-1-git-send-email-namhyung@gmail.com>
On 2010-09-16 05:55, Namhyung Kim wrote:
> 2nd argument of blk_rq_aligned() has changed to 'unsigned long' by
> previous commit 'block: fix an address space warning in blk-map.c'.
> According to that change, its caller has to be modified. This also
> removes address space warnings from sparse.
Thanks, in the future please ensure that you have all{yes,mod}config
tested patches you submit.
--
Jens Axboe
next prev parent reply other threads:[~2010-09-16 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 3:30 linux-next: build warning after merge of the block tree Stephen Rothwell
2010-09-16 3:55 ` [PATCH] block: fix an warning of calling blk_rq_aligned() Namhyung Kim
2010-09-16 6:23 ` Jens Axboe [this message]
2010-09-16 14:03 ` Namhyung Kim
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=4C91B7C4.6030802@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).