From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata : Add 40pin "short" cable support, honour drive side speed detection
Date: Thu, 24 Aug 2006 10:41:55 -0400 [thread overview]
Message-ID: <44EDBAB3.3000404@pobox.com> (raw)
In-Reply-To: <1156431385.3007.153.camel@localhost.localdomain>
Alan Cox wrote:
> Ar Iau, 2006-08-24 am 09:51 -0400, ysgrifennodd Jeff Garzik:
>> The standard policy, in place since you began, has been to push core
>> stuff into #upstream, and the driver side into #pata-drivers.
>
> Jeff, I've no problem with putting it in upstream but all this talk of
> "standard policy" is crap. Or at least "standard policy" is a concept
> existing only in Jeff's brain and not documented clearly externally in
> this case...
The pata-drivers branch has never received any libata*.[ch] changes in
its entire lifetime, and you've no doubt noticed libata*.[ch] PATA work
appearing in the upstream kernel, even when pata_*.c continues to not
exist in the upstream kernel. Core stuff has always been split up;
maybe I just didn't say that explicitly. Its pretty self-evident by
looking at public commits, though.
Jeff
prev parent reply other threads:[~2006-08-24 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 19:23 [PATCH] libata : Add 40pin "short" cable support, honour drive side speed detection Alan Cox
2006-08-24 6:56 ` Jeff Garzik
2006-08-24 10:57 ` Alan Cox
2006-08-24 13:51 ` Jeff Garzik
2006-08-24 14:56 ` Alan Cox
2006-08-24 14:41 ` Jeff Garzik [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=44EDBAB3.3000404@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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.