From: Takashi Iwai <tiwai@suse.de>
To: Raghu Ballappa Bankapur <quic_rbankapu@quicinc.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>,
Krishna Jha <quic_kkishorj@quicinc.com>
Subject: Re: [PATCH V0 1/1] asoc: msm: use hashtable to check kcontrol
Date: Mon, 13 Jun 2022 12:02:35 +0200 [thread overview]
Message-ID: <87fsk898zo.wl-tiwai@suse.de> (raw)
In-Reply-To: <6b665002-b68e-5392-a7ff-908a1c853663@quicinc.com>
On Mon, 13 Jun 2022 11:19:05 +0200,
Raghu Ballappa Bankapur wrote:
>
> Hi Takashi
>
> v2 patch looks fine. Can we use this patch to submit to android common
> kernel? There is code freeze for KMI on june 17.
If nothing reported, I'm going to merge the v3 patch (already posted)
to for-next branch for 5.19 kernel in this week. Let's see :)
thanks,
Takashi
>
> Please share your opinion.
>
>
> Thanks
>
> Raghu Bankapur
>
> On 6/10/2022 11:31 AM, Takashi Iwai wrote:
> > On Thu, 09 Jun 2022 20:16:52 +0200,
> > Raghu Ballappa Bankapur wrote:
> >>
> >> Hi Takashi
> >>
> >> Our implementation also falls inline with your approach [PATCH RFC] ALSA:
> >> control: Use xarray for faster lookups (kernel.org), but you approach looks to
> >> be clean with xarray.
> >>
> >> is it possible to upstream those changes?
> > I submitted a v2 patch, please check it out.
> >
> >
> > thanks,
> >
> > Takashi
>
next prev parent reply other threads:[~2022-06-13 10:03 UTC|newest]
Thread overview: 11+ 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 [this message]
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 ` [PATCH V0 0/1] " Mark Brown
[not found] <cover.1654252861.git.quic_rbankapu@quicinc.com>
2022-06-03 10:42 ` [PATCH V0 1/1] " Raghu Bankapur
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=87fsk898zo.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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