From: Jens Axboe <axboe@kernel.dk>
To: akpm@linux-foundation.org
Cc: hsweeten@visionengravers.com, hartleys@visionengravers.com,
philipp.reisner@linbit.com, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [patch 1/1] drivers/block/drbd/drbd_nl.c: use bitmap_parse instead of __bitmap_parse
Date: Tue, 02 Aug 2011 12:44:05 +0200 [thread overview]
Message-ID: <4E37D4F5.7050203@kernel.dk> (raw)
In-Reply-To: <201107282052.p6SKq1TZ007835@imap1.linux-foundation.org>
On 2011-07-28 22:52, akpm@linux-foundation.org wrote:
> From: H Hartley Sweeten <hartleys@visionengravers.com>
>
> The buffer 'sc.cpu_mask' is a kernel buffer. If bitmap_parse is used
> instead of __bitmap_parse the extra parameter that indicates a kernel
> buffer is not needed.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2011-08-02 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 20:52 [Drbd-dev] [patch 1/1] drivers/block/drbd/drbd_nl.c: use bitmap_parse instead of __bitmap_parse akpm
2011-08-02 10:44 ` Jens Axboe [this message]
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=4E37D4F5.7050203@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=drbd-dev@lists.linbit.com \
--cc=hartleys@visionengravers.com \
--cc=hsweeten@visionengravers.com \
--cc=philipp.reisner@linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox