From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] ftgmac100: Mostly rewrite the driver
Date: Sat, 01 Apr 2017 08:14:27 +1100 [thread overview]
Message-ID: <1490994867.3177.241.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170331135207.GG22609@lunn.ch>
On Fri, 2017-03-31 at 15:52 +0200, Andrew Lunn wrote:
> > We're running some more testing tonight, if it's all solid I'll shoot
> > it out tomorrow or sunday. Dave, it's ok to just spam the list with a
> > 55 patches series like that ?
>
> Hi Ben
>
> Is there a good reason to spam the list with 55 patches? The patches
> should be incremental, so getting them reviewed and applied in batches
> of 10 should not be a problem.
They are incremental, but some of them are trivial and in the end
it's the end result that matters but yes I could probably split some
misc stuff, rx path, tx path, and more misc.
I found an issue with link down vs. pending tx packets last night
so I need to fix that and test. I'll send things when that's done.
Cheers,
Ben.
next prev parent reply other threads:[~2017-03-31 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 4:40 [PATCH net] ftgmac100: Mostly rewrite the driver Benjamin Herrenschmidt
2017-03-29 4:57 ` David Miller
2017-03-29 5:03 ` Benjamin Herrenschmidt
2017-03-29 5:10 ` David Miller
2017-03-29 5:18 ` Benjamin Herrenschmidt
2017-03-29 18:08 ` Florian Fainelli
2017-03-29 21:08 ` Benjamin Herrenschmidt
2017-03-30 0:46 ` Benjamin Herrenschmidt
2017-03-30 3:15 ` David Miller
2017-03-31 9:59 ` Benjamin Herrenschmidt
2017-03-31 13:52 ` Andrew Lunn
2017-03-31 21:14 ` Benjamin Herrenschmidt [this message]
2017-03-31 21:56 ` Andrew Lunn
2017-03-31 16:56 ` David Miller
2017-03-29 17:42 ` kbuild test robot
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=1490994867.3177.241.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
/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).