DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alan Elder <alan.elder@microsoft.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	Long Li <longli@microsoft.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>, stephen <stephen@networkplumber.org>
Subject: RE: [EXTERNAL] Re: [PATCH v6] net/netvsc: fix parsing of VLAN metadata
Date: Mon, 19 Feb 2024 09:34:41 +0000	[thread overview]
Message-ID: <PA4PR83MB052663E55B8C55BDDF2DD01297512@PA4PR83MB0526.EURPRD83.prod.outlook.com> (raw)
In-Reply-To: <8139ddff-aabf-4ee0-a51b-a2a658691624@amd.com>

On 2/16/2024 11:40 AM, Ferruh Yigit:
> I missed v6 but put some comment on v5, briefly can you please split the patch for lib/net and driver?

I've tried to split the patch - hopefully got the formatting right - please let me know if not (it's my first time submitting a patch and I don't have all the tooling set up)

  parent reply	other threads:[~2024-02-19  9:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 15:09 [PATCH v3] " Alan Elder
2024-02-09  1:18 ` Long Li
2024-02-09 15:50   ` [PATCH v4] " Alan Elder
2024-02-14 22:17     ` Long Li
2024-02-15 11:46       ` Ferruh Yigit
2024-02-15 18:12         ` [PATCH v5] " Alan Elder
2024-02-15 18:25           ` Stephen Hemminger
2024-02-16  9:43           ` [PATCH v6] " Alan Elder
2024-02-16 11:39             ` Ferruh Yigit
2024-02-19  9:31               ` [PATCH v7 0/2] " Alan Elder
2024-02-19  9:31               ` [PATCH v7 1/2] lib/net: " Alan Elder
2024-02-19 11:12                 ` Ferruh Yigit
2024-02-19 11:14                   ` Ferruh Yigit
2024-02-19  9:31               ` [PATCH v7 2/2] net/netvsc: " Alan Elder
2024-02-19 11:12                 ` Ferruh Yigit
2024-02-19  9:34               ` Alan Elder [this message]
2024-02-16 11:33           ` [PATCH v5] " Ferruh Yigit

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=PA4PR83MB052663E55B8C55BDDF2DD01297512@PA4PR83MB0526.EURPRD83.prod.outlook.com \
    --to=alan.elder@microsoft.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=longli@microsoft.com \
    --cc=stephen@networkplumber.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).