linux-kernel - Re: [PATCH v2 0/2] can: tcan4x5x: add option for selecting nWKRQ voltage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241113193709.395c18b0@kernel.org>
Date: Wed, 13 Nov 2024 19:37:09 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Sean Nyekjaer <sean@...nix.com>, 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 Tue, 12 Nov 2024 08:16:02 +0100 Marc Kleine-Budde wrote:
> > > 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"

Yup, prefix would make it easy for us to automatically discard !

> > 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

My bad actually, I didn't realize we don't have an X: entries
on net/can/ under general networking in MAINTAINERS.

Would you mind if I added them?