From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <teheo@novell.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Marcus Meissner <meissner@novell.com>
Subject: Re: [PATCH #upstream-fixes 1/2] libata: cosmetic updates
Date: Tue, 21 Jul 2009 12:08:01 -0400 [thread overview]
Message-ID: <4A65E7E1.3010705@garzik.org> (raw)
In-Reply-To: <4A65DF92.5050305@novell.com>
Tejun Heo wrote:
> Tejun Heo wrote:
>> We're about to add more SATA_* and ATA_ACPI_FILTER_* constants.
>> Reformat them in preparation.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>
> I was about to send the second patch which filters out the offending
> commands by default but now that I think more about it I think it
> would be better to specifically blacklist the machine. So, please
> don't commit the first patch. I'll re-post later along with updated
> patch.
Will do...
prev parent reply other threads:[~2009-07-21 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 15:12 [PATCH #upstream-fixes 1/2] libata: cosmetic updates Tejun Heo
2009-07-21 15:32 ` Tejun Heo
2009-07-21 16:08 ` 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=4A65E7E1.3010705@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=meissner@novell.com \
--cc=teheo@novell.com \
/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).