[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241112-hulking-smiling-pug-c6fd4d-mkl@pengutronix.de>
Date: Tue, 12 Nov 2024 08:16:02 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Sean Nyekjaer <sean@...nix.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/2] can: tcan4x5x: add option for selecting nWKRQ
voltage
On 12.11.2024 07:39:12, Sean Nyekjaer wrote:
> On Mon, Nov 11, 2024 at 10:10:11AM +0100, Jakub Kicinski wrote:
> > On Mon, 11 Nov 2024 09:54:48 +0100 Sean Nyekjaer wrote:
> > > This series adds support for setting the nWKRQ voltage.
> >
> > There is no need to CC netdev@ on pure drivers/net/can changes.
> > Since these changes are not tagged in any way I have to manually
> > go and drop all of them from our patchwork.
Does the prefix "can-next" help, i.e.:
| [PATCH can-next v2 0/2]
which can be configured via:
| b4 prep --set-prefixes "can-next"
> Oh sorry for that.
> I'm using b4's --auto-to-cc feature, any way to fix that?
You can manually trim the list of Cc: using:
| b4 prep --edit-cover
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists