From: Jakub Kicinski <kuba@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH RESEND] net: mdio: mux-gpio: use gpiod_multi_set_value_cansleep
Date: Wed, 11 Jun 2025 13:52:49 -0700 [thread overview]
Message-ID: <20250611135249.69c88f5d@kernel.org> (raw)
In-Reply-To: <55bba029-9243-439d-9f1c-985f48ad2ec8@baylibre.com>
On Wed, 11 Jun 2025 13:40:25 -0500 David Lechner wrote:
> > It is not surprising it did not get picked up when it is mixed in with
> > a lot of other subsystems. Please always post a patchset per
> > subsystem.
> >
> > This also appears to be version 4.
> >
> > Since you did not annotate the Subject: line with the tree this is
> > for, i'm not sure the CI system will accept it an run the tests.
> >
> > https://patchwork.kernel.org/project/netdevbpf/patch/20250611-net-mdio-mux-gpio-use-gpiod_multi_set_value_cansleep-v1-1-6eb5281f1b41@baylibre.com/
> >
> > https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
>
> OK, I will try again tomorrow with [PATCH net-next v5].
No need, just keep it in mind for the future (CI managed to guess
correctly).
next prev parent reply other threads:[~2025-06-11 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 18:11 [PATCH RESEND] net: mdio: mux-gpio: use gpiod_multi_set_value_cansleep David Lechner
2025-06-11 18:25 ` Andrew Lunn
2025-06-11 18:40 ` David Lechner
2025-06-11 20:52 ` Jakub Kicinski [this message]
2025-06-13 1:50 ` patchwork-bot+netdevbpf
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=20250611135249.69c88f5d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dlechner@baylibre.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).