From: David Miller <davem@davemloft.net>
To: xiong@qca.qualcomm.com
Cc: rodrigue@qca.qualcomm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, qca-linux-team@qualcomm.com,
nic-devel@qualcomm.com, kgiori@qca.qualcomm.com,
chris.snook@gmail.com, mathieu@qca.qualcomm.com,
bryanh@quicinc.com
Subject: Re: [PATCH] net: add QCA alx Ethernet driver
Date: Tue, 28 Feb 2012 22:32:58 -0500 (EST) [thread overview]
Message-ID: <20120228.223258.2261979237568571219.davem@davemloft.net> (raw)
In-Reply-To: <157393863283F442885425D2C454285619415561@nasanexd02a.na.qualcomm.com>
From: "Huang, Xiong" <xiong@qca.qualcomm.com>
Date: Wed, 29 Feb 2012 03:11:14 +0000
> We understand your concern. To support the new chipset, do you
> think it's reasonable to upstream it as a new driver, not a
> replacement ?
It depends upon how similar the chips are.
To be honest tg3, as one example, supports quite a large array of
different pieces of hardware that use the same logical core.
So that would be my litmus test about how different a chip needs
to be to deserve an entirely new driver.
I strongly suggest you try to get atl1c working properly.
next prev parent reply other threads:[~2012-02-29 3:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 1:50 [PATCH] net: add QCA alx Ethernet driver Luis R. Rodriguez
2012-02-29 1:50 ` [PATCH] net: add new QCA alx ethernet driver which supercedes atl1c Luis R. Rodriguez
2012-02-29 1:58 ` David Miller
2012-02-29 1:53 ` [PATCH] net: add QCA alx Ethernet driver David Miller
2012-02-29 2:12 ` Luis R. Rodriguez
2012-02-29 2:15 ` David Miller
2012-02-29 2:19 ` Huang, Xiong
2012-02-29 2:28 ` David Miller
2012-02-29 3:11 ` Huang, Xiong
2012-02-29 3:32 ` David Miller [this message]
2012-02-29 7:30 ` Huang, Xiong
2012-02-29 9:38 ` Luis R. Rodriguez
2012-03-22 1:28 ` Luis R. Rodriguez
2012-03-22 9:27 ` Francois Romieu
2012-03-22 13:38 ` Luis R. Rodriguez
2012-03-30 17:10 ` Luis R. Rodriguez
2012-03-30 20:45 ` David Miller
2012-03-30 20:52 ` Luis R. Rodriguez
2012-02-29 3:32 ` Stephen Hemminger
2012-03-01 23:40 ` Francois Romieu
2012-03-02 0:56 ` Joe Perches
2012-02-29 3:52 ` Joe Perches
[not found] ` <CAA93jw4NwHaLazxK2Eo6a6TuvF3svqdZjTpHUwOyEHv-Q=busQ@mail.gmail.com>
2012-03-30 18:31 ` Luis R. Rodriguez
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=20120228.223258.2261979237568571219.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bryanh@quicinc.com \
--cc=chris.snook@gmail.com \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu@qca.qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--cc=qca-linux-team@qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=xiong@qca.qualcomm.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).