From: Alan Cox <alan@redhat.com>
To: Peter Missel <peter.missel@onlinehome.de>
Cc: Alan Cox <alan@redhat.com>, jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata.h: Don't do a SATA check for 40wire_relaxed
Date: Sat, 15 Dec 2007 12:49:51 -0500 [thread overview]
Message-ID: <20071215174951.GA16691@devserv.devel.redhat.com> (raw)
In-Reply-To: <200712151835.33275.peter.missel@onlinehome.de>
On Sat, Dec 15, 2007 at 06:35:32PM +0100, Peter Missel wrote:
> Pinging ... don't take this personal guys, but are we going to keep the
> original, dangerously broken implementation in 2.6.24, or will my patch go
> upstream in time?
Up to Jeff/Linus.
Alan (on holiday)
next prev parent reply other threads:[~2007-12-15 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 17:35 [PATCH] ata.h: Don't do a SATA check for 40wire_relaxed Peter Missel
2007-12-15 17:49 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-08 14:55 Peter Missel
2007-11-19 15:24 Alan Cox
2007-11-24 1:23 ` Jeff Garzik
2007-11-24 13:46 ` Alan Cox
2007-12-04 19:20 ` Jeff Garzik
2007-12-04 20:29 ` Alan Cox
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=20071215174951.GA16691@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=peter.missel@onlinehome.de \
/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).