From: Greg KH <gregkh@linuxfoundation.org>
To: George Valkov <gvalkov@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Foster Snowhill <forst@pen.gy>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
patchwork-bot+netdevbpf@kernel.org,
Simon Horman <simon.horman@corigine.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
linux-usb <linux-usb@vger.kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4 1/4] usbnet: ipheth: fix risk of NULL pointer deallocation
Date: Fri, 9 Jun 2023 13:09:19 +0200 [thread overview]
Message-ID: <2023060907-matted-dorsal-af5e@gregkh> (raw)
In-Reply-To: <07CBE5ED-2569-450D-975A-64B5670D6928@gmail.com>
On Fri, Jun 09, 2023 at 01:42:09PM +0300, George Valkov wrote:
> Thank you David!
>
> Can you please also backport the patch-series to Linux kernel 5.15, which is in use by the OpenWRT project! The patches apply cleanly.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2023-06-09 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 13:56 [PATCH net-next v4 1/4] usbnet: ipheth: fix risk of NULL pointer deallocation Foster Snowhill
2023-06-07 13:57 ` [PATCH net-next v4 2/4] usbnet: ipheth: transmit URBs without trailing padding Foster Snowhill
2023-06-07 13:57 ` [PATCH net-next v4 3/4] usbnet: ipheth: add CDC NCM support Foster Snowhill
2023-06-07 13:57 ` [PATCH net-next v4 4/4] usbnet: ipheth: update Kconfig description Foster Snowhill
2023-06-09 9:30 ` [PATCH net-next v4 1/4] usbnet: ipheth: fix risk of NULL pointer deallocation patchwork-bot+netdevbpf
2023-06-09 10:42 ` George Valkov
2023-06-09 11:09 ` Greg KH [this message]
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=2023060907-matted-dorsal-af5e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=forst@pen.gy \
--cc=gvalkov@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).