From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories
Date: Thu, 8 Nov 2018 07:16:28 -0800 [thread overview]
Message-ID: <20181108151628.GH56134@atomide.com> (raw)
In-Reply-To: <20181108083754.1746-1-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti•com> [181108 08:36]:
> 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.
Good to see this :) Yes merging these changes via the ASoC tree makes
sense to me. I will take a look and ack when you post the version
without RFC.
Regards,
Tony
next prev parent reply other threads:[~2018-11-08 15:16 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 ` Tony Lindgren [this message]
2018-11-26 11:25 ` [RFC 0/9] ASoC/ARM: Merge the davinci and omap audio directories Sekhar Nori
2018-11-11 16:37 ` Jarkko Nikula
2018-11-12 13:38 ` Peter Ujfalusi
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=20181108151628.GH56134@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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