From: Florian Fainelli <florian@openwrt.org>
To: David Miller <davem@davemloft.net>
Cc: sshtylyov@ru.mvista.com, ralf@linux-mips.org,
manuel.lauss@googlemail.com, linux-mips@linux-mips.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] au1000_eth platform device/driver conversion
Date: Thu, 30 Jul 2009 22:13:59 +0200 [thread overview]
Message-ID: <200907302214.00525.florian@openwrt.org> (raw)
In-Reply-To: <20090730.131000.259116391.davem@davemloft.net>
Hi,
Le Thursday 30 July 2009 22:10:00 David Miller, vous avez écrit :
> From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Date: Thu, 30 Jul 2009 23:48:13 +0400
>
> > Because they were only posted to linux-mips. And we didn't see #2 and
> > #4 in linux-mips either.
>
> That's not going to work.
>
> You can't apply some of these patches to one tree, and some to
> the other. That leaves the driver in a half-baked state in BOTH
> trees during the entire development period.
Sorry about that I did not want to "spam" netdev with MIPS specific bits as I
know those specific changes would lead to a discussion for sure.
>
> So one of the two trees has to be chosen and all 4 patches added
> there, and there only.
Ok, I got to respin them to address some comments on the MIPS-side anyway and
will not forget to CC netdev and you this time.
--
Best regards, Florian Fainelli
Email: florian@openwrt.org
Web: http://openwrt.org
IRC: [florian] on irc.freenode.net
-------------------------------
next prev parent reply other threads:[~2009-07-30 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 21:00 [PATCH 0/4] au1000_eth platform device/driver conversion Florian Fainelli
2009-07-30 19:34 ` David Miller
2009-07-30 19:48 ` Sergei Shtylyov
2009-07-30 20:10 ` David Miller
2009-07-30 20:13 ` Florian Fainelli [this message]
2009-07-30 20:17 ` David Miller
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=200907302214.00525.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=davem@davemloft.net \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=sshtylyov@ru.mvista.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).