From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, <tony@atomide.com>,
<nsekhar@ti.com>
Cc: <alsa-devel@alsa-project.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <jsarha@ti.com>
Subject: Re: [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories
Date: Mon, 12 Nov 2018 15:38:17 +0200 [thread overview]
Message-ID: <812b333e-cd01-ba32-8daa-7783072cb613@ti.com> (raw)
In-Reply-To: <1065fb8a-a8ec-fbe3-83eb-a308072ef6d6@bitmer.com>
On 2018-11-11 18:37, Jarkko Nikula wrote:
> On 11/8/18 10:37 AM, Peter Ujfalusi wrote:
>> The series also includes patches to updated the arch/arm/ files (defconfigs,
>> source files using audio Kconfig symbols).
>>
>> I believe with v1 all of this can be merged via ASoC tree as the chances of
>> conflicts are low for the touched arch/arm files. But Sekhar and Tony can
>> correct me if I'm wrong.
>>
>> I think I have catched all (I hope) issues regarding to Kconfig thanks to the
>> various autobuild machines out there kindly testing my linux-next-wip branch.
>>
>> I would appreciate any testing comments before I send the v1!
>>
> I applied on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git commit
> abd97b7c53ac ("Merge branch 'asoc-4.21' into asoc-next").
>
> Patches 2 and 6 didn't apply and 7-8 I skipped. For my functional
> testing none of those were required.
Hrm, the series was based on next-20181019, but I will keep on eye on these!
> For the sound/soc/{omap => ti} conversion you may add:
>
> Tested-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
> Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
Thank you!
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2018-11-12 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 8:37 [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories Peter Ujfalusi
2018-11-08 8:37 ` [RFC 1/9] ASoC: ti: Merge davinci and omap directories Peter Ujfalusi
2018-11-08 8:37 ` [RFC 2/9] MAINTAINERS: Add entry for sound/soc/ti and update the OMAP audio support Peter Ujfalusi
2018-11-08 8:37 ` [RFC 3/9] ARM: OMAP1: Makefile: Update for new MCBSP Kconfig option Peter Ujfalusi
2018-11-08 8:37 ` [RFC 4/9] ARM: OMAP2: " Peter Ujfalusi
2018-11-08 8:37 ` [RFC 5/9] ARM: davinci: dm365-evm: Update for the new ASoC Kcofnig options Peter Ujfalusi
2018-11-08 8:37 ` [RFC 6/9] ARM: omap2plus_defconfig: Update the audio options Peter Ujfalusi
2018-11-08 8:37 ` [RFC 7/9] ARM: omap1_defconfig: Do not select ASoC by default Peter Ujfalusi
2018-11-08 8:37 ` [RFC 8/9] ARM: davinci_all_defconfig: Update the audio options Peter Ujfalusi
2018-11-08 8:37 ` [RFC 9/9] ASoC: ti: Kconfig: Remove the deprecated options Peter Ujfalusi
2018-11-08 15:16 ` [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories Tony Lindgren
2018-11-26 11:25 ` Sekhar Nori
2018-11-11 16:37 ` Jarkko Nikula
2018-11-12 13:38 ` Peter Ujfalusi [this message]
2018-11-13 22:46 ` 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=812b333e-cd01-ba32-8daa-7783072cb613@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.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;
as well as URLs for NNTP newsgroup(s).