From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
linux-ide@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>
Subject: Re: OOPS with 2.6.21rc2-git (ata: conflict with ide0/1)
Date: Fri, 09 Mar 2007 19:31:56 +0900 [thread overview]
Message-ID: <45F1379C.9090609@gmail.com> (raw)
In-Reply-To: <45EFDEF6.7000909@garzik.org>
Jeff Garzik wrote:
> Which patch?
>
> Since this affects libata directly, and since devres came in via libata,
> I would rather that libata bugs not get /too/ blocked by patches in
> other trees.
This one.
http://article.gmane.org/gmane.linux.kernel/495515
--
tejun
prev parent reply other threads:[~2007-03-09 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 22:32 OOPS with 2.6.21rc2-git (ata: conflict with ide0/1) Kok, Auke
2007-03-08 8:05 ` Tejun Heo
2007-03-08 10:01 ` Jeff Garzik
2007-03-09 10:31 ` Tejun Heo [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=45F1379C.9090609@gmail.com \
--to=htejun@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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).