From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Tejun Heo <htejun@gmail.com>
Cc: "\"J.A. Magallón\"" <jamagallon@ono.com>,
"Linux-Kernel," <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, "Jeff Garzik" <jgarzik@pobox.com>,
"Andrew Morton" <akpm@osdl.org>
Subject: Re: [2.6.18-rc2-mm1] libata ate one PATA channel
Date: Mon, 31 Jul 2006 17:31:29 +0100 [thread overview]
Message-ID: <1154363489.7230.61.camel@localhost.localdomain> (raw)
In-Reply-To: <44CE2908.8080502@gmail.com>
Ar Maw, 2006-08-01 am 01:00 +0900, ysgrifennodd Tejun Heo:
> These are patches #110-112. Andrew, can you drop those patches for the
> time being? I'm working on integrating those into libata #upstream now.
If you drop the host_set and tuning patches please drop all the PATA
stuff and my other patches out. I don't have time to field a second
batch of hundreds of "why has my drive stopped working, why is the speed
wrong" emails.
It'll be easier just to work outside the -mm tree with all this
continued in/out random breakage if people are just going to say "drop
xyz patch" rather than actually specifying *what is actually wrong* and
getting me to fix the merge (Tejun that last one sentence is a hint ;))
Alan
next prev parent reply other threads:[~2006-07-31 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 11:45 [2.6.18-rc2-mm1] libata ate one PATA channel J.A. Magallón
2006-07-30 19:53 ` Tejun Heo
2006-07-31 15:24 ` J.A. Magallón
2006-07-31 16:00 ` Tejun Heo
2006-07-31 16:31 ` Alan Cox [this message]
2006-07-31 16:50 ` Tejun Heo
2006-07-31 17:03 ` Tejun Heo
2006-07-31 18:52 ` Alan Cox
2006-07-31 18:52 ` Tejun Heo
2006-07-31 19:05 ` Jeff Garzik
2006-07-31 18:38 ` Alan Cox
2006-07-31 21:41 ` J.A. Magallón
2006-08-01 6:22 ` Andrew Morton
2006-08-01 7:32 ` 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=1154363489.7230.61.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=htejun@gmail.com \
--cc=jamagallon@ono.com \
--cc=jgarzik@pobox.com \
--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).