From: Scott Bauer <scott.bauer@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: keith.busch@intel.com, jonathan.derrick@intel.com, axboe@fb.com,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] block/sed-opal: tone down not supported warnings
Date: Thu, 16 Feb 2017 13:43:36 -0700 [thread overview]
Message-ID: <20170216204335.GA3732@sbauer-Z170X-UD5> (raw)
In-Reply-To: <20170216201053.1190-1-hch@lst.de>
On Thu, Feb 16, 2017 at 09:10:52PM +0100, Christoph Hellwig wrote:
> Not having OPAL or a sub-feature supported is an entirely normal
> condition for many drives, so don't warn about it. Keep the messages,
> but tone them down to debug only.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Scott Bauer <scott.bauer@intel.com>
prev parent reply other threads:[~2017-02-16 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 20:10 [PATCH 1/2] block/sed-opal: tone down not supported warnings Christoph Hellwig
2017-02-16 20:10 ` [PATCH 2/2] block/sed-opal: allocate struct opal_dev dynamically Christoph Hellwig
2017-02-16 20:47 ` Scott Bauer
2017-02-17 8:58 ` Johannes Thumshirn
2017-02-17 9:11 ` Christoph Hellwig
2017-02-17 9:14 ` Johannes Thumshirn
2017-02-16 20:43 ` Scott Bauer [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=20170216204335.GA3732@sbauer-Z170X-UD5 \
--to=scott.bauer@intel.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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