mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Zhangfei Gao <zhangfei.gao@oss.qualcomm.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	shengchao.guo@oss.qualcomm.com,
	mohammad.rafi.shaik@oss.qualcomm.com,
	bartosz.golaszewski@oss.qualcomm.com,
	Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>,
	Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>,
	linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ASoC: qcom: audioreach: support multichannel PCM formats
Date: Tue, 10 Nov 2026 12:11:52 +0000	[thread overview]
Message-ID: <7195c2b6-e1d7-4816-b86c-55e1936e11a2@sirena.org.uk> (raw)
In-Reply-To: <CAFkd8hvXor7A5zaRtH5iQm6NsphzsxrjbADcRwedsONo=6J2gA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

On Tue, Nov 10, 2026 at 03:59:44PM +0800, Zhangfei Gao wrote:
> On Wed, Oct 28, 2026 at 10:47 AM Zhangfei Gao
> <zhangfei.gao@oss.qualcomm.com> wrote:
> >
> > AudioReach currently rejects PCM streams with more than four channels in
> > the PCM and shared-memory media format paths.


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 delete unneeded context from mails when replying.  Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-11-10 12:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  8:25 [PATCH v2] " Zhangfei Gao
2026-10-27  8:46 ` Prasad Kumpatla
2026-10-27  9:55   ` Zhangfei Gao
2026-10-27 11:45     ` Prasad Kumpatla
2026-10-27 13:47 ` Srinivas Kandagatla
2026-10-28  2:40   ` Zhangfei Gao
2026-10-28  2:47 ` [PATCH v3] " Zhangfei Gao
2026-11-04  3:40   ` Shawn Guo
2026-11-10  7:59   ` Zhangfei Gao
2026-11-10 12:11     ` Mark Brown [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=7195c2b6-e1d7-4816-b86c-55e1936e11a2@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mohammad.rafi.shaik@oss.qualcomm.com \
    --cc=perex@perex.cz \
    --cc=prasad.kumpatla@oss.qualcomm.com \
    --cc=shengchao.guo@oss.qualcomm.com \
    --cc=srini@kernel.org \
    --cc=srinivas.kandagatla@oss.qualcomm.com \
    --cc=tiwai@suse.com \
    --cc=zhangfei.gao@oss.qualcomm.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

all inboxes | Powered by JetHome®