From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Georgi Valkov <gvalkov@abv.bg>
Cc: linux-usb <linux-usb@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"stable @ vger . kernel . org" <stable@vger.kernel.org>,
Yves-Alexis Perez <corsac@corsac.net>
Subject: [PATCH v2 0/1] ipheth URB overflow fix
Date: Tue, 1 Feb 2022 08:16:17 +0100 [thread overview]
Message-ID: <cover.1643699778.git.jan.kiszka@siemens.com> (raw)
Resent (v1 was mangled).
Note that the "Fixes:" tag is a strong assumption of mine. Speak up if
you think that is wrong.
Jan
Georgi Valkov (1):
ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
drivers/net/usb/ipheth.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-01 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 7:16 Jan Kiszka [this message]
2022-02-01 7:16 ` [PATCH v2 1/1] ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback Jan Kiszka
2022-02-02 4:30 ` [PATCH v2 0/1] ipheth URB overflow fix patchwork-bot+netdevbpf
2022-02-02 8:09 ` Yves-Alexis Perez
2022-02-02 10:35 ` Georgi Valkov
2022-02-02 17:01 ` Yves-Alexis Perez
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=cover.1643699778.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=corsac@corsac.net \
--cc=davem@davemloft.net \
--cc=gvalkov@abv.bg \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.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).