From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: dmaengine <dmaengine@vger.kernel.org>,
alsa-devel@alsa-project.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v3 4/4] ASoC: Intel: rename SND_SST_MFLD_PLATFORM to SND_SST_MID_PLATFORM
Date: Tue, 3 Jan 2017 09:08:16 +0530 [thread overview]
Message-ID: <20170103033815.GA3573@localhost> (raw)
In-Reply-To: <c5228e73-d5cf-e4cd-b78b-24334e1fb5f3@linux.intel.com>
On Mon, Jan 02, 2017 at 10:05:40AM -0600, Pierre-Louis Bossart wrote:
>
>
> On 01/02/2017 09:20 AM, Andy Shevchenko wrote:
> >Rename SND_SST_MFLD_PLATFORM to SND_SST_MID_PLATFORM to make it clear that is
> >not only about Medfield platform.
> Does this change make sense? Medfield was a completely different
> platform and lumping everything under the same Kconfig option
> doesn't seem right to me... Plus we've stopped using 'mid' for
> years, no one would know what it stands for. The only clear
> architecture feature is the presence of the switch matrix that
> uniquely identifies all platforms based on Baytrail, Cherrytrail,
> Merrifield and Anniedale. Medfield/Clovertrail did not expose a
> switch matrix.
Mea culpa..
So we started this with medfield and the driver construction is pretty much
the same untill skylake. So clubbing under mfld bucket made sense to me.
MID is not flavour of the season now.
If anyone comes with a better name, am for that :)
--
~Vinod
next prev parent reply other threads:[~2017-01-03 3:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 15:20 [PATCH v3 0/4] ASoC: Intel: clean up Kconfig Andy Shevchenko
2017-01-02 15:20 ` [PATCH v3 1/4] ASoC: Intel: select DW_DMAC_CORE since it's mandatory Andy Shevchenko
2017-01-03 2:00 ` Keyon Jie
2017-01-02 15:20 ` [PATCH v3 2/4] ASoC: Intel: remove redundant select SND_SOC_INTEL_SST Andy Shevchenko
2017-01-17 18:45 ` Applied "ASoC: Intel: remove redundant select SND_SOC_INTEL_SST" to the asoc tree Mark Brown
2017-01-02 15:20 ` [PATCH v3 3/4] ASoC: Intel: remove ignored dependencies Andy Shevchenko
2017-01-17 18:45 ` Applied "ASoC: Intel: remove ignored dependencies" to the asoc tree Mark Brown
2017-01-02 15:20 ` [PATCH v3 4/4] ASoC: Intel: rename SND_SST_MFLD_PLATFORM to SND_SST_MID_PLATFORM Andy Shevchenko
2017-01-02 16:05 ` Pierre-Louis Bossart
2017-01-03 3:38 ` Vinod Koul [this message]
2017-01-03 14:18 ` Pierre-Louis Bossart
2017-01-04 10:44 ` Andy Shevchenko
2017-01-04 16:58 ` Pierre-Louis Bossart
2017-01-05 3:53 ` Vinod Koul
2017-01-05 8:41 ` Andy Shevchenko
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=20170103033815.GA3573@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@linux.intel.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).