From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
chunbo.luo@windriver.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH #upstream-fixes] libata: update atapi disable handling
Date: Thu, 31 Jul 2008 01:50:54 -0400 [thread overview]
Message-ID: <489152BE.8030309@garzik.org> (raw)
In-Reply-To: <4890F0B8.90009@kernel.org>
Tejun Heo wrote:
> Global and per-LLD ATAPI disable checks were done in the command issue
> path probably because it was left out during EH conversion. On
> affected machines, this can cause lots of warning messages. Move them
> to where they belong - the probing path.
>
> Reported by Chunbo Luo.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Chunbo Luo <chunbo.luo@windriver.com>
> ---
> drivers/ata/libata-core.c | 12 +++++++++++-
> drivers/ata/libata-scsi.c | 34 ++--------------------------------
> drivers/ata/libata.h | 1 -
> 3 files changed, 13 insertions(+), 34 deletions(-)
applied
prev parent reply other threads:[~2008-07-31 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 22:52 [PATCH #upstream-fixes] libata: update atapi disable handling Tejun Heo
2008-07-31 5:50 ` 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=489152BE.8030309@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=chunbo.luo@windriver.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).