From: "Steven J. Hill" <Steven.Hill@cavium.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v10 3/4] netdev: octeon-ethernet: Add Cavium Octeon III support.
Date: Wed, 9 May 2018 14:29:56 -0500 [thread overview]
Message-ID: <d6af3617-2fc4-d89e-4533-ddc85a6d64c8@cavium.com> (raw)
In-Reply-To: <20180508.222824.409067086455315118.davem@davemloft.net>
On 05/08/2018 09:28 PM, David Miller wrote:
>
> That's all I have the stomache for at the moment.
>
> This thing is really large, making it nearly impossible to review
> as one huge patch #3. Perhaps you can find a way to split it up
> logically somehow?
>
Hey David.
This code was inherited by me, so there a lot of parts I personally
have not looked at. The third patch indeed needs to be broken up.
Let me devote some hours to cleaning, splitting and simplifying. My
apologies for the time you spent looking at it. The first patch,
however, only makes changes in the existing 'staging' directory. It
seems like that one could go in without trouble? Cheers.
Steve
next prev parent reply other threads:[~2018-05-09 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 17:22 [PATCH net-next v10 0/4] netdev: octeon-ethernet: Add Cavium Octeon III support Steven J. Hill
2018-05-07 17:22 ` [PATCH net-next v10 1/4] staging: octeon: Remove USE_ASYNC_IOBDMA macro Steven J. Hill
2018-05-07 17:22 ` [PATCH net-next v10 2/4] dt-bindings: Add Cavium Octeon Common Ethernet Interface Steven J. Hill
2018-05-07 17:22 ` [PATCH net-next v10 3/4] netdev: octeon-ethernet: Add Cavium Octeon III support Steven J. Hill
2018-05-09 2:28 ` David Miller
2018-05-09 19:29 ` Steven J. Hill [this message]
2018-05-07 17:22 ` [PATCH net-next v10 4/4] MAINTAINERS: Add entry for drivers/net/ethernet/cavium/octeon/octeon3-* Steven J. Hill
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=d6af3617-2fc4-d89e-4533-ddc85a6d64c8@cavium.com \
--to=steven.hill@cavium.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.