From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: dapm-graph: add component on/off and route names to graph
Date: Wed, 21 Aug 2024 10:17:48 +0200 [thread overview]
Message-ID: <20240821101748.41799c5a@booty> (raw)
In-Reply-To: <c4e2580f-1675-48b0-b59f-a076eced7675@sirena.org.uk>
Hello Mark,
On Tue, 20 Aug 2024 18:04:17 +0100
Mark Brown <broonie@kernel.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@bootlin.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
next prev parent reply other threads:[~2024-08-21 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 7:41 [PATCH 0/3] ASoC: dapm-graph: add component on/off and route names to graph Luca Ceresoli
2024-06-07 7:41 ` [PATCH 1/3] ASoC: dapm-graph: remove the "ROOT" cluster Luca Ceresoli
2024-06-07 7:41 ` [PATCH 2/3] ASoC: dapm-graph: visualize component On/Off bias level Luca Ceresoli
2024-06-07 7:41 ` [PATCH 3/3] ASoC: dapm-graph: show path name for non-static routes Luca Ceresoli
2024-08-20 16:44 ` [PATCH 0/3] ASoC: dapm-graph: add component on/off and route names to graph Luca Ceresoli
2024-08-20 17:04 ` Mark Brown
2024-08-21 8:17 ` Luca Ceresoli [this message]
2024-08-21 12:56 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240821101748.41799c5a@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox