From: Tejun Heo <tj@kernel.org>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ahci: Use dev_info() to inform about the lack of Device Sleep support
Date: Fri, 9 Jan 2015 16:54:01 -0500 [thread overview]
Message-ID: <20150109215401.GG2785@htj.dyndns.org> (raw)
In-Reply-To: <1420742494-5017-1-git-send-email-gabriele.mzt@gmail.com>
On Thu, Jan 08, 2015 at 07:41:34PM +0100, Gabriele Mazzotta wrote:
> According to the Serial ATA AHCI specification, Device Sleep is an
> optional feature and as such no errors should be printed if it's
> missing. Keep informing users, but use dev_info() instead of dev_err().
Does this condition actually occur? The cap's advertise that the
controller does DEVSLP but the port register doesn't have it?
Thanks.
--
tejun
prev parent reply other threads:[~2015-01-09 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:41 [PATCH] ahci: Use dev_info() to inform about the lack of Device Sleep support Gabriele Mazzotta
2015-01-09 21:54 ` Tejun Heo [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=20150109215401.GG2785@htj.dyndns.org \
--to=tj@kernel.org \
--cc=gabriele.mzt@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).