From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH #upstream-fixes] libata-acpi: missing _SDD is not an error
Date: Fri, 20 Nov 2009 03:48:22 -0500 [thread overview]
Message-ID: <4B0657D6.3000004@garzik.org> (raw)
In-Reply-To: <4B03F585.3090000@kernel.org>
On 11/18/2009 08:24 AM, Tejun Heo wrote:
> Missing _SDD is not an error. Don't treat it as one.
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Reported-by: Takashi Iwai<tiwai@suse.de>
> ---
> drivers/ata/libata-acpi.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
hmmmm, do you have a link to the bug report?
How critical is this? Is it a regression fix?
We are very late into 2.6.32-rc, where we try to minimize the patches
applied as much as possible.
Jeff
next prev parent reply other threads:[~2009-11-20 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 13:24 [PATCH #upstream-fixes] libata-acpi: missing _SDD is not an error Tejun Heo
2009-11-19 23:36 ` Jeff Garzik
2009-11-20 8:48 ` Jeff Garzik [this message]
2009-11-20 8:56 ` Takashi Iwai
2009-11-20 8:58 ` Jeff Garzik
2009-11-20 8:58 ` Tejun Heo
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=4B0657D6.3000004@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tiwai@suse.de \
--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).