From: "malin (R)" <malin89@huawei.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Arseniy Krasnov <avkrasnov@salutedevices.com>,
tanjingguo <tanjingguo@huawei.com>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"eperezma@redhat.com" <eperezma@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
Chenzhe <chenzhe@huawei.com>,
cenxianlong <cenxianlong@huawei.com>,
cuirongzhen <cuirongzhen@huawei.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] vsock/virtio: bind uarg before filling zerocopy skb
Date: Wed, 27 May 2026 02:42:23 +0000 [thread overview]
Message-ID: <bd2b60d9ee5d4edfae4a7ce58ace71a4@huawei.com> (raw)
Hello Jakub,
> The email headers are duplicated on this patch.
> This appears to confuse git am into thinking the patch is empty:
>
> $ git am mbox
> Patch is empty.
>
> Please fix this and repost (please add the review tags you already
> received in the repost)
My bad. I have sent the right post with git command.
https://lore.kernel.org/netdev/20260527023301.1075581-1-malin89@huawei.com/T/#u
Please let me know if there is any other problem.
Thanks
Lin
next reply other threads:[~2026-05-27 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 2:42 malin (R) [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 11:15 [PATCH net] vsock/virtio: bind uarg before filling zerocopy skb malin (R)
2026-05-25 11:25 ` Arseniy Krasnov
2026-05-25 11:25 ` Michael S. Tsirkin
2026-05-25 12:48 ` Stefano Garzarella
2026-05-27 1:46 ` Jakub Kicinski
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=bd2b60d9ee5d4edfae4a7ce58ace71a4@huawei.com \
--to=malin89@huawei.com \
--cc=avkrasnov@salutedevices.com \
--cc=cenxianlong@huawei.com \
--cc=chenzhe@huawei.com \
--cc=cuirongzhen@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=tanjingguo@huawei.com \
--cc=virtualization@lists.linux.dev \
--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 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.