From: Kees Cook <keescook@chromium.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Justin Stitt <justinstitt@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: Re: [PATCH v2] net: dsa: lan9303: use ethtool_sprintf() for lan9303_get_strings()
Date: Fri, 1 Dec 2023 10:19:04 -0800 [thread overview]
Message-ID: <202312011018.478B0E750@keescook> (raw)
In-Reply-To: <20231130224021.41d1d453@kernel.org>
On Thu, Nov 30, 2023 at 10:40:21PM -0800, Jakub Kicinski wrote:
> On Thu, 30 Nov 2023 13:59:58 -0800 Kees Cook wrote:
> > Applied to for-next/hardening, thanks!
> >
> > [1/1] net: dsa: lan9303: use ethtool_sprintf() for lan9303_get_strings()
> > https://git.kernel.org/kees/c/f1c7720549bf
>
> Please drop this, it got changes requested on our end because
> I figured Alexander's comment is worth addressing.
Done. Justin, can you please refresh this patch (or, actually, make sure
the ethtool_puts() series lands?)
--
Kees Cook
next prev parent reply other threads:[~2023-12-01 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:56 [PATCH v2] net: dsa: lan9303: use ethtool_sprintf() for lan9303_get_strings() Justin Stitt
2023-10-05 22:42 ` Kees Cook
2023-10-06 9:37 ` Alexander Lobakin
2023-11-30 21:59 ` Kees Cook
2023-12-01 6:40 ` Jakub Kicinski
2023-12-01 18:19 ` Kees Cook [this message]
2023-12-07 19:51 ` Justin Stitt
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=202312011018.478B0E750@keescook \
--to=keescook@chromium.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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.