From: Dave Jones <davej@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pata_via: Cable detect error
Date: Sat, 16 Dec 2006 11:16:47 -0500 [thread overview]
Message-ID: <20061216161647.GG23368@redhat.com> (raw)
In-Reply-To: <45841525.7040406@pobox.com>
On Sat, Dec 16, 2006 at 10:47:49AM -0500, Jeff Garzik wrote:
> I think it's #upstream-fixes material (-rc material), and applied as such.
>
> Especially considering that libata pata_* drivers are not the primary
> drivers, I think it's best to forward this type of stuff, especially as
> it is indeed IMO a fix worth having.
They may not be primary today, but it's not going to be very long
at all before that situation changes. AFAIK, most of (if not all) the major
distros basing on 2.6.19+ are moving to using the libata PATA drivers in
their next releases.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-12-16 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 14:32 [PATCH] pata_via: Cable detect error Alan
2006-12-16 15:47 ` Jeff Garzik
2006-12-16 16:16 ` Dave Jones [this message]
2006-12-16 16:29 ` Jeff Garzik
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=20061216161647.GG23368@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).