From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Dax Kelson <dax@gurulabs.com>, Greg KH <gregkh@suse.de>,
James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@osdl.org>,
Theodore Bullock <tbullock@nortel.com>,
robm@fastmail.fm, brong@fastmail.fm, erich@areca.com.tw,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Areca arcmsr kernel integration for 2.6.18?
Date: Thu, 24 Aug 2006 12:41:27 +0100 [thread overview]
Message-ID: <1156419687.3007.98.camel@localhost.localdomain> (raw)
In-Reply-To: <1156408443.3014.40.camel@laptopd505.fenrus.org>
Ar Iau, 2006-08-24 am 10:34 +0200, ysgrifennodd Arjan van de Ven:
> > The current Fedora Core 6 development (and consequently RHEL5 and
> > CentOS5) is using 2.6.18-rc kernels (actually as of yesterday, your git
> > tree).
>
> .. and those distros can't pull in this driver because..... ?
FC6 policy is to follow upstream very closely. RHEL may vary.
I don't think its fair to ask Greg to make this decision and James has
already given a clear answer.
Alan
next prev parent reply other threads:[~2006-08-24 11:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 18:07 Areca arcmsr kernel integration Theodore Bullock
2006-07-28 20:27 ` Greg KH
2006-07-29 1:48 ` Bron Gondwana
2006-07-29 2:14 ` Robert Mueller
2006-07-31 21:32 ` Theodore Bullock
2006-08-01 3:03 ` Andrew Morton
2006-08-02 14:53 ` James Bottomley
2006-08-23 23:25 ` Areca arcmsr kernel integration for 2.6.18? Dax Kelson
2006-08-24 0:20 ` Adrian Bunk
2006-08-24 3:42 ` Greg KH
2006-08-24 5:56 ` Dax Kelson
2006-08-24 8:34 ` Arjan van de Ven
2006-08-24 11:41 ` Alan Cox [this message]
2006-08-24 16:21 ` Theodore Bullock
2006-08-24 16:59 ` Greg KH
2006-08-24 4:11 ` James Bottomley
2006-08-24 6:34 ` Dax Kelson
2006-09-29 4:11 ` Bron Gondwana
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=1156419687.3007.98.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=brong@fastmail.fm \
--cc=dax@gurulabs.com \
--cc=erich@areca.com.tw \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robm@fastmail.fm \
--cc=tbullock@nortel.com \
/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.