From: David Miller <davem@davemloft.net>
To: steven.hill@cavium.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III network driver.
Date: Sun, 29 Apr 2018 20:33:47 -0400 (EDT) [thread overview]
Message-ID: <20180429.203347.679522174405836744.davem@davemloft.net> (raw)
In-Reply-To: <1524785414-19236-1-git-send-email-steven.hill@cavium.com>
From: "Steven J. Hill" <steven.hill@cavium.com>
Date: Thu, 26 Apr 2018 18:30:10 -0500
> We want to add the Cavium OCTEON-III network driver. But since
> interacting with the input and output queues is done via special CPU
> local memory, we also need to add support to the MIPS/Octeon
> architecture code. Aren't SoCs nice in this way? These are the
> prerequisite patches that are needed before the network driver can be
> merged.
I don't know if we really want all of these MIPS specific changes to
go via the net-next tree.
The right way to do this is probably getting this series into the MIPS
architecture tree.
Then when that hits Linus's tree, and finally ends up merging into
the networking tree, you can submit the networking driver.
next prev parent reply other threads:[~2018-04-30 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 23:30 [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III network driver Steven J. Hill
2018-04-26 23:30 ` [PATCH net-next v9 1/4] MIPS: Octeon: Enable LMTDMA/LMTST operations Steven J. Hill
2018-04-26 23:30 ` [PATCH net-next v9 2/4] MIPS: Octeon: Automatically provision CVMSEG space Steven J. Hill
2018-04-26 23:30 ` [PATCH net-next v9 3/4] staging: octeon: Remove USE_ASYNC_IOBDMA macro Steven J. Hill
2018-04-26 23:30 ` [PATCH net-next v9 4/4] MIPS: Octeon: Add a global resource manager Steven J. Hill
2018-04-30 0:33 ` David Miller [this message]
2018-05-02 18:19 ` [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III network driver 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=20180429.203347.679522174405836744.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steven.hill@cavium.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).