linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 00/15] net: thunderx: Add support for 81xx and 83xx
Date: Sun, 31 Jul 2016 20:36:41 -0700 (PDT)	[thread overview]
Message-ID: <20160731.203641.335462360411404621.davem@davemloft.net> (raw)
In-Reply-To: <CA+sq2CfGDgw=4VuhUfnKEwKkLrEXxKMWmEX4P5hKSsj4pmBGXA@mail.gmail.com>

From: Sunil Kovvuri <sunil.kovvuri@gmail.com>
Date: Mon, 1 Aug 2016 08:59:16 +0530

> Understood but unfortunately I don't see these patches in patchwork.
> http://patchwork.ozlabs.org/project/netdev/list/?submitter=&state=*&q=thunderx&archive=both&delegate=
> http://patchwork.ozlabs.org/project/netdev/list/?submitter=62159&state=*&q=&archive=both&delegate=

Then you'll need to resubmit them.

But net-next is closed at this time, so new feature submissions are
not appropriate.  You need to wait until the net-next tree opens
again.

      reply	other threads:[~2016-08-01  3:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 12:58 [PATCH v3 00/15] net: thunderx: Add support for 81xx and 83xx sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 01/15] net: thunderx: Moved HW capability info from macros to structure sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 02/15] net: thunderx: Add VNIC's PCI devid on future chips sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 03/15] net: thunderx: Add support for 81xx and 83xx chips sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 04/15] net: thunderx: Set queue count based on number of CPUs sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 05/15] net: thunderx: Enable CQE_RX desc's extension fields sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 06/15] net: thunderx: Enable mailbox interrupts on 81xx/83xx sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 07/15] net: thunderx: Support for different LMAC types within BGX sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 08/15] net: thunderx: Add 81xx support to BGX driver sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 09/15] net: thunderx: Add QSGMII interface type support sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 10/15] net: thunderx: Add RGMII " sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 11/15] net: thunderx: Use netdev's name for naming VF's interrupts sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 12/15] net: thunderx: Use skb_add_rx_frag() for split buffer Rx pkts sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 13/15] net: thunderx: Improvement for MBX interface debug messages sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 14/15] net: thunderx: Reset RXQ HW stats when interface is brought down sunil.kovvuri at gmail.com
2016-07-15 12:58 ` [PATCH v3 15/15] net: thunderx: Don't set mac address for secondary Qset VFs sunil.kovvuri at gmail.com
2016-07-21  5:58 ` [PATCH v3 00/15] net: thunderx: Add support for 81xx and 83xx Sunil Kovvuri
2016-07-31 16:44   ` Sunil Kovvuri
2016-07-31 18:54     ` David Miller
2016-08-01  3:29       ` Sunil Kovvuri
2016-08-01  3:36         ` David Miller [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=20160731.203641.335462360411404621.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.infradead.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).