From: Vladimir Oltean <olteanv@gmail.com>
To: Justin Stitt <justinstitt@google.com>
Cc: GR-Linux-NIC-Dev@marvell.com, UNGLinuxDriver@microchip.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, oss-drivers@corigine.com,
linux-hyperv@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, bpf@vger.kernel.org
Subject: Re: [PATCH next v2 1/3] ethtool: Implement ethtool_puts()
Date: Fri, 27 Oct 2023 01:25:48 +0300 [thread overview]
Message-ID: <20231026222548.rqbp5ktgo2mysl6w@skbuf> (raw)
In-Reply-To: <CAFhGd8rWOE8zGFCdjM6i8H3TP8q5BFFxMGCk0n-nmLmjHojefg@mail.gmail.com>
On Thu, Oct 26, 2023 at 03:09:59PM -0700, Justin Stitt wrote:
> Should I undo this? I want my patch against next since it's targeting
> some stuff in-flight over there. BUT, I also want ethtool_puts() to be
> directly below ethtool_sprintf() in the source code. What to do?
(removing everyone except the lists from CC, I don't want to go to email
arest because of spamming too many recipients)
What is the stuff in-flight in next that this is targeting?
And why would anything prevent you from putting ethtool_puts() directly
below ethtool_sprintf()?
next prev parent reply other threads:[~2023-10-26 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 21:56 [PATCH next v2 0/3] ethtool: Add ethtool_puts() Justin Stitt
2023-10-26 21:56 ` [PATCH next v2 1/3] ethtool: Implement ethtool_puts() Justin Stitt
2023-10-26 22:02 ` Vladimir Oltean
2023-10-26 22:09 ` Justin Stitt
2023-10-26 22:11 ` Justin Stitt
2023-10-26 22:21 ` Vladimir Oltean
2023-10-26 22:25 ` Vladimir Oltean [this message]
2023-10-27 19:38 ` Justin Stitt
2023-10-26 21:56 ` [PATCH next v2 2/3] checkpatch: add ethtool_sprintf rules Justin Stitt
2023-10-26 22:12 ` Vladimir Oltean
2023-10-26 22:24 ` Justin Stitt
2023-10-26 22:33 ` Vladimir Oltean
2023-10-26 22:38 ` Joe Perches
2023-10-27 19:40 ` Justin Stitt
2023-10-27 21:57 ` Joe Perches
2023-10-26 21:56 ` [PATCH next v2 3/3] treewide: Convert some ethtool_sprintf() to ethtool_puts() Justin Stitt
2023-10-26 22:17 ` Vladimir Oltean
2023-10-27 0:24 ` [PATCH next v2 0/3] ethtool: Add ethtool_puts() Andrew Lunn
2023-10-27 19:32 ` 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=20231026222548.rqbp5ktgo2mysl6w@skbuf \
--to=olteanv@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bpf@vger.kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=justinstitt@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@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