[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a6319e40-8782-490e-8506-3ee71fa64c15@intel.com>
Date: Fri, 23 Aug 2024 14:37:12 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Tony Nguyen <anthony.l.nguyen@...el.com>, <davem@...emloft.net>,
<pabeni@...hat.com>, <edumazet@...gle.com>, <netdev@...r.kernel.org>,
<przemyslaw.kitszel@...el.com>, <joshua.a.hay@...el.com>,
<michal.kubiak@...el.com>, <nex.sw.ncis.osdt.itp.upstreaming@...el.com>,
"Jose E . Marchesi" <jose.marchesi@...cle.com>
Subject: Re: [PATCH net-next v2 1/9] unroll: add generic loop unroll helpers
From: Jakub Kicinski <kuba@...nel.org>
Date: Thu, 22 Aug 2024 15:59:46 -0700
> On Thu, 22 Aug 2024 17:15:25 +0200 Alexander Lobakin wrote:
>>> Please run the submissions thru get_maintainers
>>
>> I always do that. get_maintainers.pl gives nobody for linux/unroll.h.
>
> You gotta feed it the *patch*, not the path. For keyword matching on the
Oops, sorry. I always do that for patches, not paths, but here I wanted
to use a shortcut not thinking that it may give completely different
results =\
> contents. I wanted to print a warning when people use get_maintainer
> with a path but Linus blocked it. I'm convinced 99% of such uses are
> misguided.
>
> But TBH I was directing the message at Tony as well. Please just feed
> the patches to get_maintainer when posting.
Thanks,
Olek
Powered by blists - more mailing lists