From: Jakub Kicinski <kuba@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Kees Cook <kees@kernel.org>,
linux-hardening@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jay Vosburgh <jv@jvosburgh.net>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next] drivers/net/bonding: User strscpy() to copy device name
Date: Mon, 8 Jun 2026 14:18:22 -0700 [thread overview]
Message-ID: <20260608141822.780fb5c5@kernel.org> (raw)
In-Reply-To: <20260608220710.7499931d@pumpkin>
On Mon, 8 Jun 2026 22:07:10 +0100 David Laight wrote:
> On Mon, 8 Jun 2026 13:23:11 -0700
> Jakub Kicinski <kuba@kernel.org> wrote:
>
> > On Sat, 6 Jun 2026 21:26:07 +0100 david.laight.linux@gmail.com wrote:
> > > From: David Laight <david.laight.linux@gmail.com>
> >
> > Could you be so very kind to read the automated message you received
> > when you posted this?
>
> Looks like I managed to send two patches for files in the same directory
> that contained equivalent fixes.
>
> I think I should be able to merge the patch emails into one and send
> as a single V2 patch that contains both changes.
Not what I asked you.
You seem to be following the ML yet you excreted a bunch of incorrectly
formatted and likely useless patches. Read the email. Start with one
or two submissions at a time.
next prev parent reply other threads:[~2026-06-08 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 20:26 [PATCH net-next] drivers/net/bonding: User strscpy() to copy device name david.laight.linux
2026-06-08 20:23 ` Jakub Kicinski
2026-06-08 21:07 ` David Laight
2026-06-08 21:18 ` Jakub Kicinski [this message]
2026-06-08 21:40 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2026-06-06 20:26 david.laight.linux
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=20260608141822.780fb5c5@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox