Linux Sound subsystem development
 help / color / mirror / Atom feed
From: HariKrishna Sagala <hariconscious@gmail.com>
To: Mark Brown <broonie@kernel.org>,
	 HariKrishna Sagala <hariconscious@gmail.com>
Cc: lgirdwood@gmail.com, peter.ujfalusi@linux.intel.com,
	 yung-chuan.liao@linux.intel.com,
	ranjani.sridharan@linux.intel.com,  daniel.baluta@nxp.com,
	kai.vehmanen@linux.intel.com,  pierre-louis.bossart@linux.dev,
	shuah@kernel.org, perex@perex.cz,  tiwai@suse.com,
	sound-open-firmware@alsa-project.org,
	 linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/soc/sof:Use kmalloc_array instead of kmalloc
Date: Thu, 27 Nov 2025 17:44:30 +0530 (IST)	[thread overview]
Message-ID: <f8e4e44a-4ae9-694a-9fd4-bb6d5ebb8057@gmail.com> (raw)
In-Reply-To: <80668037-20f0-4f56-b0fe-388b26563361@sirena.org.uk>


On Thu, 27 Nov 2025, Mark Brown wrote:

> On Thu, Nov 27, 2025 at 10:35:34AM +0530, HariKrishna Sagala wrote:
>
> > Just checking in to see if you had a chance to review this.
> > If it is missed in the box, please let me know.
>
> 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.
>

Thank you for the clarification and the expected review cadence.
I understand people will be busy with the commitments.
Sorry for reminding for a non-critical patch but I followed-up after 2
weeks.

I will resend the patch as per the subsystem style.
I didn't send this earlier as I followed as per suggestion not to send the
patch again for only a commit message change.
Going forward I will avoid this and allow reasonable time for review
unless a change is urgent.

Thank you for the guidance.

      reply	other threads:[~2025-11-27 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 14:25 [PATCH] sound/soc/sof:Use kmalloc_array instead of kmalloc hariconscious
2025-10-15 19:08 ` Mark Brown
2025-11-06  9:40   ` HariKrishna Sagala
2025-11-27  5:05     ` HariKrishna Sagala
2025-11-27 11:12       ` Mark Brown
2025-11-27 12:14         ` HariKrishna Sagala [this message]

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=f8e4e44a-4ae9-694a-9fd4-bb6d5ebb8057@gmail.com \
    --to=hariconscious@gmail.com \
    --cc=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=shuah@kernel.org \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.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