From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: skip suppress reporting if ATA_EHI_QUIET
Date: Tue, 09 Oct 2007 21:40:58 -0400 [thread overview]
Message-ID: <470C2DAA.4090209@garzik.org> (raw)
In-Reply-To: <20071009055756.GG12186@htj.dyndns.org>
Tejun Heo wrote:
> ATA_EHI_NO_AUTOPSY and ATA_EHI_QUIET are used during initial probing
> to skip exception analysis and reporting. Usually, there's nothing to
> report but on some allowed but rare corner cases (e.g. phy status
> changed interrupt when IRQ is enabled on frozen port - this happens if
> IRQ pending status isn't cleared in the IRQ router or controller)
> exception messages get printed.
>
> Skip reporting if ATA_EHI_QUIET is set.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-eh.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
applied
prev parent reply other threads:[~2007-10-10 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 5:57 [PATCH] libata: skip suppress reporting if ATA_EHI_QUIET Tejun Heo
2007-10-10 1:40 ` Jeff Garzik [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=470C2DAA.4090209@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=linux-ide@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).