From: Mark Brown <broonie@kernel.org>
To: Raghu Bankapur <quic_rbankapu@quicinc.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Krishna Jha <quic_kkishorj@quicinc.com>
Subject: Re: [PATCH V0 0/1] asoc: msm: use hashtable to check kcontrol
Date: Mon, 30 May 2022 16:08:24 +0200 [thread overview]
Message-ID: <YpTP2JOlCiYb3lBf@sirena.org.uk> (raw)
In-Reply-To: <cover.1653813866.git.quic_rbankapu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Sun, May 29, 2022 at 02:20:08PM +0530, Raghu Bankapur wrote:
> use hashtabe instead of linear list to check kcontrol before
> adding them for improving early audio KPI.
Please don't send cover letters for single patches, if there is anything
that needs saying put it in the changelog of the patch or after the ---
if it's administrative stuff. This reduces mail volume and ensures that
any important information is recorded in the changelog rather than being
lost.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-30 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 8:50 [PATCH V0 0/1] asoc: msm: use hashtable to check kcontrol Raghu Bankapur
2022-05-29 8:50 ` [PATCH V0 1/1] " Raghu Bankapur
2022-05-29 9:35 ` Takashi Iwai
[not found] ` <f3a25238-fcc6-2381-e329-0bd80a3632a5@quicinc.com>
2022-06-10 6:01 ` Takashi Iwai
2022-06-13 9:19 ` Raghu Ballappa Bankapur
2022-06-13 10:02 ` Takashi Iwai
2022-05-29 10:40 ` kernel test robot
2022-05-30 14:13 ` Mark Brown
2022-05-31 4:46 ` kernel test robot
2022-05-30 14:08 ` 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=YpTP2JOlCiYb3lBf@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_kkishorj@quicinc.com \
--cc=quic_rbankapu@quicinc.com \
--cc=tiwai@suse.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