All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: alan@lxorguk.ukuu.org.uk, jamagallon@ono.com,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	jgarzik@pobox.com
Subject: Re: [2.6.18-rc2-mm1] libata ate one PATA channel
Date: Tue, 01 Aug 2006 16:32:27 +0900	[thread overview]
Message-ID: <44CF038B.50809@gmail.com> (raw)
In-Reply-To: <20060731232243.65468eec.akpm@osdl.org>

Andrew Morton wrote:
> On Tue, 1 Aug 2006 01:50:11 +0900
> Tejun Heo <htejun@gmail.com> wrote:
> 
>>> 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 ;))
>> Okay, took the hint.  Magallon, can you please try the following
>> patch?
> 
> Gee that's a big scary patch.  Is it considered ready for -mm?  (bearing in
> mind -mm's exacting quality standards (heh, I kill me)).
> 

It's still a bit broken.  I'll follow up with better patches later today 
(hopefully :)

Thanks.

-- 
tejun

      reply	other threads:[~2006-08-01  7:32 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
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 [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=44CF038B.50809@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.