From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@osdl.org
Subject: Re: [PATCH] libata: Cable detection fixes
Date: Fri, 02 Mar 2007 17:50:03 -0500 [thread overview]
Message-ID: <45E8AA1B.6000803@garzik.org> (raw)
In-Reply-To: <20070302124534.5fcfec9f@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> However, given that we are in -rc cycle, and the wide impact of this
>> change, this patch wants splitting. The ->cable_detect stuff should be
>> in a separate patch from the IDENTIFY DEVICE ordering stuff. This
>> ensures sanity when git-bisecting changes, and allows fast-tracking of
>> the identify-ordering change.
>
> Fine by me - I carefully sent Linus the hook but no changes using it and
> sent those changes just to the list/you.
The implication was that you should revise, sign-off, and resend, like
all the other kernel developers do when they receive feedback during
engineering review...
Nonetheless, I extracted and applied the patch I mention above, and will
send it upstream today.
Jeff
next prev parent reply other threads:[~2007-03-02 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 17:30 [PATCH] libata: Cable detection fixes Alan
2007-03-02 1:24 ` Linus Torvalds
2007-03-02 1:33 ` Jeff Garzik
2007-03-02 6:35 ` Michal Jaegermann
2007-03-02 12:52 ` Alan Cox
2007-03-02 1:26 ` Jeff Garzik
2007-03-02 12:45 ` Alan Cox
2007-03-02 22:50 ` Jeff Garzik [this message]
2007-03-02 22:48 ` Jeff Garzik
2007-03-03 19:35 ` Paul Rolland
2007-03-03 19:35 ` Paul Rolland
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=45E8AA1B.6000803@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--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 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.