public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	tony@atomide.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
	Merlijn Wajer <merlijn@wizzup.org>
Subject: Re: [RFC PATCH] soc: audio-graph-card2: use correct endpoint when getting link parameters
Date: Mon, 13 Jan 2025 18:24:18 +0200	[thread overview]
Message-ID: <9cc6c2ad-0811-482d-91c8-d162bd7f09f4@gmail.com> (raw)
In-Reply-To: <f4a65ffc-7f0d-4d45-83b9-2377cb00f3b1@sirena.org.uk>

Hi,


On 13.01.25 г. 15:40 ч., Mark Brown wrote:
> On Mon, Jan 13, 2025 at 07:55:30AM +0200, Ivaylo Dimitrov wrote:
>> ping
> 
> 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.
> 
> 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.
> 
> Please don't top post, reply in line with needed context.  This allows
> readers to readily follow the flow of conversation and understand what
> you are talking about and also helps ensure that everything in the
> discussion is being addressed.

I understand people are busy, but I also see community sent patches 
being treated with low priority, or being silently ignored too often 
lately, but lets not go into that.

I sent that RFC patch on 20.12.2024, today is 13.10.2025 - if this is 
not a reasonable time, well, what is? By the same time I sent 2 other 
patches and they are already in -next. In the meanwhile I see patches 
sent in the morning to be reviewed till the end of the day - not 
critical bugfixes patches but new functionality.

Also, I don't understand how the ping was content free, given that it 
was on top of the original patch, unless I don't get what "content free" 
is supposed to mean, possible, I am not native English speaker.


Regards,
Ivo

  reply	other threads:[~2025-01-13 16:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  7:11 [RFC PATCH] soc: audio-graph-card2: use correct endpoint when getting link parameters Ivaylo Dimitrov
2025-01-13  5:55 ` Ivaylo Dimitrov
2025-01-13 13:40   ` Mark Brown
2025-01-13 16:24     ` Ivaylo Dimitrov [this message]
2025-01-13 17:01       ` Mark Brown
2025-01-13 21:38         ` Ivaylo Dimitrov
2025-01-14  6:44 ` Kuninori Morimoto
2025-01-14  9:04   ` Ivaylo Dimitrov
2025-01-14 23:49     ` Kuninori Morimoto
2025-01-15  6:10       ` Ivaylo Dimitrov
2025-01-20 16:27       ` [PATCH] ASoC: " Ivaylo Dimitrov
2025-01-20 23:35         ` Kuninori Morimoto
2025-01-21  6:23           ` Ivaylo Dimitrov
2025-01-21  6:48           ` [PATCH v2] " Ivaylo Dimitrov
2025-01-21 12:18             ` Mark Brown
2025-01-21 13:33               ` Ivaylo Dimitrov
2025-01-21 13:41                 ` Mark Brown
2025-01-21 23:22             ` Kuninori Morimoto
2025-01-23 11:29             ` 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=9cc6c2ad-0811-482d-91c8-d162bd7f09f4@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=merlijn@wizzup.org \
    --cc=pavel@ucw.cz \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=tony@atomide.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