From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: Mark Brown <broonie@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Kaczmarski, Filip" <filip.kaczmarski@intel.com>,
"N, Harshapriya" <harshapriya.n@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"ppapierkowski@habana.ai" <ppapierkowski@habana.ai>,
"Barlik, Marcin" <marcin.barlik@intel.com>,
"zwisler@google.com" <zwisler@google.com>,
"pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"Proborszcz, Filip" <filip.proborszcz@intel.com>,
"amadeuszx.slawinski@linux.intel.com"
<amadeuszx.slawinski@linux.intel.com>,
"Wasko, Michal" <michal.wasko@intel.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"Hejmowski, Krzysztof" <krzysztof.hejmowski@intel.com>,
"cujomalainey@chromium.org" <cujomalainey@chromium.org>,
"Gopal, Vamshi Krishna" <vamshi.krishna.gopal@intel.com>
Subject: RE: [PATCH v10 14/14] ASoC: Intel: Select catpt and deprecate haswell
Date: Fri, 2 Oct 2020 08:32:34 +0000 [thread overview]
Message-ID: <347145dee59c4dab900da84724382769@intel.com> (raw)
In-Reply-To: <20201001194927.GY6715@sirena.org.uk>
On 2020-10-01 9:49 PM, Mark Brown wrote:
> On Thu, Oct 01, 2020 at 09:54:09PM +0300, Andy Shevchenko wrote:
>
>> This has a dependency from SPI tree. Can you merge (cherry-pick) one patch from
>> there to ASoC tree, please?
>
>> a2bee00cccf4 ("spi: pxa2xx: Add SSC2 and SSPSP2 SSP registers")
>
> Ah, right - that was actually mentioned in the cover letter but got
> missed (I think I didn't register that it was a SPI change and stopped
> at the "already merged" bit). It would have been helpful to highlight
> this with the SPI change so it could have been applied as a separate
> branch rather than on the main branch which would make this easier, this
> sort of stuff is why I like to have per driver branches.
>
While catpt's cover-letter mentioned this, indeed the SPI change was
devoid of such note. Sorry for that, Mark.
Is my action required?
Regards,
Czarek
next prev parent reply other threads:[~2020-10-02 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 14:12 [PATCH v10 00/14] ASoC: Intel: Catpt - Lynx and Wildcat point Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 01/14] ASoC: Intel: Add catpt base members Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 02/14] ASoC: Intel: catpt: Implement IPC protocol Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 03/14] ASoC: Intel: catpt: Add IPC message handlers Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 04/14] ASoC: Intel: catpt: Define DSP operations Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 05/14] ASoC: Intel: catpt: Firmware loading and context restore Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 06/14] ASoC: Intel: catpt: PCM operations Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 07/14] ASoC: Intel: catpt: Device driver lifecycle Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 08/14] ASoC: Intel: catpt: Event tracing Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 09/14] ASoC: Intel: catpt: Simple sysfs attributes Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 10/14] ASoC: Intel: haswell: Remove haswell-solution specific code Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 11/14] ASoC: Intel: broadwell: " Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 12/14] ASoC: Intel: bdw-5650: " Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 13/14] ASoC: Intel: bdw-5677: " Cezary Rojewski
2020-09-29 14:12 ` [PATCH v10 14/14] ASoC: Intel: Select catpt and deprecate haswell Cezary Rojewski
2020-10-01 18:33 ` Mark Brown
2020-10-01 18:54 ` Andy Shevchenko
2020-10-01 19:49 ` Mark Brown
2020-10-02 8:32 ` Rojewski, Cezary [this message]
2020-09-29 16:44 ` [PATCH v10 00/14] ASoC: Intel: Catpt - Lynx and Wildcat point Andy Shevchenko
2020-10-02 20:55 ` 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=347145dee59c4dab900da84724382769@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=filip.kaczmarski@intel.com \
--cc=filip.proborszcz@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshapriya.n@intel.com \
--cc=krzysztof.hejmowski@intel.com \
--cc=lgirdwood@gmail.com \
--cc=marcin.barlik@intel.com \
--cc=michal.wasko@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ppapierkowski@habana.ai \
--cc=tiwai@suse.com \
--cc=vamshi.krishna.gopal@intel.com \
--cc=zwisler@google.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.