linux-kernel - Re: [PATCH 0/3] ASoC: dapm-graph: add component on/off and route names to graph

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20240821101748.41799c5a@booty>
Date: Wed, 21 Aug 2024 10:17:48 +0200
From: Luca Ceresoli <luca.ceresoli@...tlin.com>
To: Mark Brown <broonie@...nel.org>
Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>, Thomas Petazzoni
 <thomas.petazzoni@...tlin.com>, linux-sound@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] ASoC: dapm-graph: add component on/off and route
 names to graph

Hello Mark,

On Tue, 20 Aug 2024 18:04:17 +0100
Mark Brown <broonie@...nel.org> wrote:

> On Tue, Aug 20, 2024 at 06:44:06PM +0200, Luca Ceresoli wrote:
> > On Fri, 07 Jun 2024 09:41:50 +0200
> > Luca Ceresoli <luca.ceresoli@...tlin.com> wrote:  
> 
> > > This small series adds some improvements to dapm-graph in order to produce
> > > a more correct and informative graph.  
> 
> > Gentle ping about this series.  
> 
> > It applies and works fine on current master.  
> 
> Please don't send content free pings and please allow a reasonable time
> for review.  People get busy, go on holiday, attend conferences and so 
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.

I'm sorry about the noise. I thought it was worth in this case because:

 * this series has been sent 2.5 months ago
 * there was no reply at all
 * AFAIK and according to MAINTAINERS there is no patchwork catching
   tools/sound/

So it was looking much more like something gone into oblivion than
being on someone's TODO list.

> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.

Apologies, my fault for not having checked the archives. Note taken.

After doing so now however, I must say that while counting the resends
is easy, counting the pings in a somewhat reliable way is very time
consuming. It would be nice to have this info in a more reachable way
(MAINTAINERS?).

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com