From: Feng Liu <feliu@nvidia.com>
To: Parav Pandit <parav@nvidia.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Simon Horman <simon.horman@corigine.com>,
Bodong Wang <bodong@nvidia.com>, William Tu <witu@nvidia.com>
Subject: Re: [PATCH net v3] virtio_net: Fix error unwinding of XDP initialization
Date: Wed, 3 May 2023 11:00:25 -0400 [thread overview]
Message-ID: <482f00d4-d3f0-da85-93e3-a4a2e5597e12@nvidia.com> (raw)
In-Reply-To: <PH0PR12MB54816403B23CE6D0AF2FD035DC6C9@PH0PR12MB5481.namprd12.prod.outlook.com>
On 2023-05-02 p.m.11:14, Parav Pandit wrote:
>
>> From: Feng Liu <feliu@nvidia.com>
>> Sent: Tuesday, May 2, 2023 8:35 PM
>
>> Issue: 3383038
> Remove this internal garbage.
>
>> Fixes: 754b8a21a96d ("virtio_net: setup xdp_rxq_info")
>> Signed-off-by: Feng Liu <feliu@nvidia.com>
>> Reviewed-by: William Tu <witu@nvidia.com>
>> Reviewed-by: Parav Pandit <parav@nvidia.com>
>> Reviewed-by: Simon Horman <simon.horman@corigine.com>
>> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
>> Change-Id: Ib4c6a97cb7b837cfa484c593dd43a435c47ea68f
> Remove this internal garbage.
> Please run a local script not to forward the above garbage in upstream patches.
>
> You are missing the changelog from v0->v1->v2->v3.
> Please add and resend with above things removed and with changelog.
ok
next prev parent reply other threads:[~2023-05-03 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:35 Feng Liu
2023-05-03 3:14 ` Parav Pandit
2023-05-03 15:00 ` Feng Liu [this message]
2023-05-06 2:33 ` Xuan Zhuo
2023-05-06 12:08 ` Feng Liu
2023-05-08 1:45 ` Xuan Zhuo
2023-05-08 15:00 ` Feng Liu
2023-05-09 1:43 ` Xuan Zhuo
2023-05-10 5:00 ` Jason Wang
2023-05-10 11:54 ` Feng Liu
2023-05-12 1:54 ` Feng Liu
2023-05-12 3:25 ` Xuan Zhuo
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=482f00d4-d3f0-da85-93e3-a4a2e5597e12@nvidia.com \
--to=feliu@nvidia.com \
--cc=bodong@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=witu@nvidia.com \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®