From: Jan Beulich <jbeulich@suse.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <stefano@stabellini.net>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: [PATCH net-next 0/2] xen-netfront: XSA-403 follow-on
Date: Wed, 13 Jul 2022 11:18:03 +0200 [thread overview]
Message-ID: <7fca0e44-43b5-8448-3653-249d117dc084@suse.com> (raw)
While investigating the XSA, I did notice a few more things. The two
patches aren't really dependent on one another.
1: remove leftover call to xennet_tx_buf_gc()
2: re-order error checks in xennet_get_responses()
Jan
next reply other threads:[~2022-07-13 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:18 Jan Beulich [this message]
2022-07-13 9:19 ` [PATCH net-next 1/2] xen-netfront: remove leftover call to xennet_tx_buf_gc() Jan Beulich
2022-07-13 9:19 ` [PATCH net-next 2/2] xen-netfront: re-order error checks in xennet_get_responses() Jan Beulich
2022-07-14 10:37 ` Paolo Abeni
2022-07-14 10:40 ` [PATCH net-next 0/2] xen-netfront: XSA-403 follow-on patchwork-bot+netdevbpf
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=7fca0e44-43b5-8448-3653-249d117dc084@suse.com \
--to=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=netdev@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=stefano@stabellini.net \
--cc=xen-devel@lists.xenproject.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 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.