From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: "Huang, Xiong" <xiong@qca.qualcomm.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
David Miller <davem@davemloft.net>,
"Ren, Cloud" <cjren@qca.qualcomm.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
qca-linux-team <qca-linux-team@qualcomm.com>,
nic-devel <nic-devel@qualcomm.com>
Subject: Re: [PATCH v2] net: add new QCA alx ethernet driver
Date: Fri, 24 Aug 2012 10:34:30 +0500 [thread overview]
Message-ID: <CAB=NE6UOG-i6O48Z+EUMgo=zTvGiGGTd9A0O-MiTJ+FnyMB_2w@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6Xg=NUsb-hQyxr+-RyzpkJ-BH6RbbcTX6KF23H+u4yEPQ@mail.gmail.com>
On Fri, Aug 24, 2012 at 8:32 AM, Luis R. Rodriguez
<rodrigue@qca.qualcomm.com> wrote:
> It would be useful for you to describe the exact functionality,
> perhaps in a separate thread or maybe even just RFC patches which you
> have to be simply ready for may just be just that -- RFC patches which
> we flush down the v2 toilet.
A simple strategy for you is for you to remove this code (if present)
for now and then throw into a crap/ patch [0] under compat-drivers but
with an objective of eventually going through the RFC stages to get
this properly merged upstream.
[0] https://backports.wiki.kernel.org/index.php/Documentation/compat-drivers/additional-patches
Luis
prev parent reply other threads:[~2012-08-24 5:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 16:42 [PATCH v2] net: add new QCA alx ethernet driver cjren
2012-08-23 5:57 ` David Miller
2012-08-23 6:35 ` Huang, Xiong
2012-08-23 6:40 ` David Miller
2012-08-23 6:56 ` Huang, Xiong
2012-08-23 7:13 ` David Miller
2012-08-23 10:28 ` Luis R. Rodriguez
2012-08-23 21:09 ` Ben Hutchings
2012-08-24 1:55 ` Huang, Xiong
2012-08-24 2:09 ` Ben Hutchings
2012-08-24 2:39 ` Huang, Xiong
2012-08-24 4:32 ` Luis R. Rodriguez
2012-08-24 5:34 ` Luis R. Rodriguez [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='CAB=NE6UOG-i6O48Z+EUMgo=zTvGiGGTd9A0O-MiTJ+FnyMB_2w@mail.gmail.com' \
--to=mcgrof@do-not-panic.com \
--cc=bhutchings@solarflare.com \
--cc=cjren@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--cc=qca-linux-team@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).