From: Thomas Gleixner <tglx@linutronix.de>
To: Roland Dreier <rdreier@cisco.com>
Cc: Greg KH <greg@kroah.com>, Arnaud Lacombe <lacombar@gmail.com>,
Anca Emanuel <anca.emanuel@gmail.com>,
Elvis Dowson <elvis.dowson@mac.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline
Date: Thu, 11 Nov 2010 01:40:54 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1011110139200.2900@localhost6.localdomain6> (raw)
In-Reply-To: <adar5esn1gd.fsf@cisco.com>
On Wed, 10 Nov 2010, Roland Dreier wrote:
> > Isn't the openwrt stuff just drivers and some arch specific code?
> > Nothing that is core infrastructure, and nothing preventing them from
> > submitting the drivers and arch code if they want to, right?
>
> Actually openwrt has some core infrastructure for managing (ethernet)
> switches as extra-fancy multiport PHYs. That means that all the drivers
> in openwrt for the typical 5-8 port switches in home routers don't
> really apply to mainline.
Why not? Those switches _ARE_ extra-fancy multiport PHYs. And AFAICT
we have no support for this stuff in mainline at all.
So where is the problem ?
Thanks,
tglx
next prev parent reply other threads:[~2010-11-11 0:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 18:18 Forked android kernel development from linux kernel mainline Elvis Dowson
2010-11-02 21:25 ` Janakiram Sistla
2010-11-06 18:12 ` Greg KH
2010-11-06 19:22 ` Ted Ts'o
2010-11-06 19:40 ` Anca Emanuel
2010-11-06 23:40 ` Ted Ts'o
2010-11-06 23:52 ` david
2010-11-07 0:03 ` Ted Ts'o
2010-11-07 0:13 ` Alan Cox
2010-11-07 0:20 ` Janakiram Sistla
2010-11-09 16:30 ` Mark Brown
2010-11-07 0:20 ` david
2010-11-10 13:54 ` Pavel Machek
2010-11-10 20:38 ` Rafael J. Wysocki
2011-01-11 14:33 ` Pavel Machek
2010-11-06 23:42 ` Janakiram Sistla
2010-11-06 23:09 ` Greg KH
2010-11-07 0:24 ` Randy Dunlap
2010-11-07 8:38 ` Elvis Dowson
2010-11-07 11:44 ` Anca Emanuel
2010-11-07 15:57 ` Greg KH
2010-11-07 20:06 ` Elvis Dowson
2010-11-07 21:31 ` Greg KH
2010-11-07 21:46 ` Arnaud Lacombe
2010-11-07 21:47 ` Arnaud Lacombe
2010-11-09 18:10 ` Elvis Dowson
2010-11-09 18:24 ` Greg KH
2010-11-09 18:37 ` Elvis Dowson
2010-11-09 18:42 ` david
2010-11-09 18:52 ` Elvis Dowson
2010-11-09 20:55 ` Ted Ts'o
2010-11-09 22:32 ` Alan Cox
2010-11-10 0:35 ` Ted Ts'o
2010-11-10 9:53 ` Florian Mickler
2010-11-10 20:55 ` Alan Cox
2010-11-07 21:44 ` Arnaud Lacombe
2010-11-07 21:59 ` Greg KH
2010-11-07 23:09 ` Arnaud Lacombe
2010-11-08 1:42 ` Greg KH
2010-11-08 2:22 ` Arnaud Lacombe
2010-11-09 13:27 ` Florian Fainelli
2010-11-11 0:33 ` Roland Dreier
2010-11-11 0:40 ` Thomas Gleixner [this message]
2010-11-12 3:15 ` Roland Dreier
2010-11-12 10:26 ` Florian Fainelli
2010-11-11 0:47 ` Greg KH
2010-11-11 11:21 ` Florian Fainelli
2010-11-12 3:17 ` Roland Dreier
2010-11-11 11:18 ` Florian Fainelli
2010-11-09 13:27 ` Florian Fainelli
2010-11-09 13:51 ` [OpenWrt-Devel] " Wolfgang Spraul
2010-11-13 3:06 ` Arnaud Lacombe
2010-11-15 17:34 ` Stefan Monnier
2010-11-16 6:23 ` Brian Swetland
2010-11-16 7:02 ` Anca Emanuel
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=alpine.LFD.2.00.1011110139200.2900@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=anca.emanuel@gmail.com \
--cc=elvis.dowson@mac.com \
--cc=greg@kroah.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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 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).