From: Jakub Kicinski <kuba@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, uwe@kleine-koenig.org
Subject: Re: [PATCH net-next 00/12] net: Complete conversion to i2c_probe_new
Date: Tue, 22 Nov 2022 10:40:11 -0800 [thread overview]
Message-ID: <20221122104011.20792b02@kernel.org> (raw)
In-Reply-To: <20221122093843.ph5prj7thbxds5n7@pengutronix.de>
On Tue, 22 Nov 2022 10:38:43 +0100 Uwe Kleine-König wrote:
> On Mon, Nov 21, 2022 at 11:15:34AM -0800, Jakub Kicinski wrote:
> > Reposting for Uwe the networking slice of his mega-series:
> > https://lore.kernel.org/all/20221118224540.619276-1-uwe@kleine-koenig.org/
> > so that our build bot can confirm the obvious.
> >
> > fix mlx5 -> mlxsw while at it.
>
> What is the relevant difference that made the build bot consider your
> resent but not my series? Is it "net-next" in the Subject?
Not all patches hit the netdev ML so the bot considered the series
incomplete, at least on our end. I'm guessing the general Intel bot
can reconstruct a partial series based on LKML.
prev parent reply other threads:[~2022-11-22 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 19:15 [PATCH net-next 00/12] net: Complete conversion to i2c_probe_new Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 01/12] net: dsa: lan9303: Convert to i2c's .probe_new() Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 02/12] net: dsa: microchip: ksz9477: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 03/12] net: dsa: xrs700x: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 04/12] net/mlxsw: " Jakub Kicinski
2022-11-21 22:20 ` kernel test robot
2022-11-22 4:33 ` Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 05/12] nfc: microread: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 06/12] nfc: mrvl: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 07/12] NFC: nxp-nci: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 08/12] nfc: pn533: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 09/12] nfc: pn544: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 10/12] nfc: s3fwrn5: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 11/12] nfc: st-nci: " Jakub Kicinski
2022-11-21 19:15 ` [PATCH net-next 12/12] nfc: st21nfca: i2c: " Jakub Kicinski
2022-11-22 9:38 ` [PATCH net-next 00/12] net: Complete conversion to i2c_probe_new Uwe Kleine-König
2022-11-22 18:40 ` Jakub Kicinski [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=20221122104011.20792b02@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=uwe@kleine-koenig.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).