From: Jens Axboe <axboe@kernel.dk>
To: John Pittman <jpittman@redhat.com>, Bart Van Assche <bvanassche@acm.org>
Cc: linux-block@vger.kernel.org, Laurence Oberman <loberman@redhat.com>
Subject: Re: [PATCH v2] null_blk: add zoned config support information
Date: Sun, 6 Jan 2019 10:58:46 -0700 [thread overview]
Message-ID: <45d53ef5-6460-e4ed-ff2d-9232c659f8f1@kernel.dk> (raw)
In-Reply-To: <CA+RJvhy1tJ93g3Ne2D4RLFRF62nU5=dWvofZpmPUa0yZt0EFhQ@mail.gmail.com>
On 1/5/19 5:44 AM, John Pittman wrote:
> Jens, Bart, It occurred to me just now that on the pr_err() message,
> "null_blk: CONFIG_BLK_DEV_ZONED not enabled" is a little better
> than "CONFIG_BLK_DEV_ZONED not enabled". It was my intent
> to include that 'null_blk:', but it slipped my mind at the last moment.
I applied it just now, and added the prefix to the error message.
--
Jens Axboe
prev parent reply other threads:[~2019-01-06 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 17:06 [PATCH v2] null_blk: add zoned config support information John Pittman
2019-01-04 21:49 ` Bart Van Assche
2019-01-05 12:44 ` John Pittman
2019-01-06 17:58 ` 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=45d53ef5-6460-e4ed-ff2d-9232c659f8f1@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=jpittman@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=loberman@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 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).