[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230825172307.7fa89fc7@kernel.org>
Date: Fri, 25 Aug 2023 17:23:07 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Junfeng Guo <junfeng.guo@...el.com>, <anthony.l.nguyen@...el.com>,
<jesse.brandeburg@...el.com>, <intel-wired-lan@...ts.osuosl.org>,
<netdev@...r.kernel.org>, <qi.z.zhang@...el.com>, <ivecera@...hat.com>,
<sridhar.samudrala@...el.com>, <horms@...nel.org>, <edumazet@...gle.com>,
<davem@...emloft.net>, <pabeni@...hat.com>
Subject: Re: [PATCH iwl-next v8 00/15] Introduce the Parser Library
On Fri, 25 Aug 2023 12:52:27 +0200 Alexander Lobakin wrote:
> > You keep breaking the posting guidelines :(
> > I already complained to people at Intel about you.
> >
> > The only way to push back that I can think of is to start handing out
> > posting suspensions for all @intel.com addresses on netdev. Please
>
> Ah, that collective responsibility :D
I'd call it delegating the responsibilities :)
> > don't make us stoop that low.
>
> But seriously, please don't. Intel is huge and we physically can't keep
> an eye on every developer or patch. I personally don't even know what
> team the submitter is from.
> Spending 8 hrs a day on tracking every @intel.com submission on
> netdev is also not something I'd like to do at work (I mean, I'd
> probably like reviewing every line coming out of my org, had I
> 120-150 hrs a day...). I know that sounds cheap, but that's how I see
> it :z
Intel may be huge, but this patch is for ice specifically. And the
author knows enough to put presumably-internally-mandated iwl-next
tag in the subject. So how about someone steps up and points them
at a manual before 4 versions are posted?
Powered by blists - more mailing lists