From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, liam.r.girdwood@intel.com,
mengdong.lin@intel.com, jarkko.nikula@intel.com,
yao.jin@intel.com, pierre-louis.bossart@intel.com
Subject: Re: [PATCH 0/5] Intel SST driver restructure
Date: Fri, 13 Mar 2015 12:02:05 +0530 [thread overview]
Message-ID: <20150313063205.GB32000@intel.com> (raw)
In-Reply-To: <20150312195420.GB28806@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]
On Thu, Mar 12, 2015 at 07:54:20PM +0000, Mark Brown wrote:
> On Thu, Mar 12, 2015 at 10:31:55PM +0800, Jie Yang wrote:
> > In order to prepare for the upstreaming of Skylake drivers and to
> > allow reuse of code between different Intel audio DSP products,
> > this patch series restructures the Intel directory as follows:
>
> This is all fine by me - I'd just like to see an ack before we do this
> from the other Intel people to make sure they're not going to get
> surprised, and also make sure that any in flight patches (particularly
> bug fixes) get merged before the rename since this will make it easier
> to apply things. Indeed, do we have an ETA for the Skylake code? If
Am working on it :) That will take time IMO, the HDA things are tricky here
and will get done first followed by ASoC core bits and then finally driver.
> it's not due before the merge window then it might be best to apply
> these (or changes like them) at the very end of this development cycle.
I think that is a good suggestion, we can send this when merge wondow closes
so no issue with in flght code
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-03-13 6:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 14:31 [PATCH 0/5] Intel SST driver restructure Jie Yang
2015-03-12 14:31 ` [PATCH 1/5] ASoC: Intel: create common folder and move common files in Jie Yang
2015-03-12 14:31 ` [PATCH 2/5] ASoC: Intel: create haswell folder and move haswell platform " Jie Yang
2015-03-12 14:31 ` [PATCH 3/5] ASoC: Intel: create boards folder and move sst boards " Jie Yang
2015-03-12 14:31 ` [PATCH 4/5] ASoC: Intel: create baytrail folder and move baytrail platform " Jie Yang
2015-03-12 14:32 ` [PATCH 5/5] ASoC: Intel: create atom folder and move atom " Jie Yang
2015-03-12 19:54 ` [PATCH 0/5] Intel SST driver restructure Mark Brown
2015-03-13 1:28 ` Jie, Yang
2015-03-13 14:32 ` Antonio Ospite
2015-03-13 6:32 ` Vinod Koul [this message]
2015-03-13 6:28 ` Vinod Koul
2015-03-13 8:19 ` Jarkko Nikula
2015-03-13 14:13 ` Jie, Yang
2015-03-13 23:34 ` Mark Brown
2015-03-14 6:04 ` Jie, Yang
2015-04-01 1:53 ` Jie, Yang
2015-04-01 7:08 ` 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=20150313063205.GB32000@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=yao.jin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.