All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Hejmowski, Krzysztof" <krzysztof.hejmowski@intel.com>,
	"Kaczmarski, Filip" <filip.kaczmarski@intel.com>,
	"N, Harshapriya" <harshapriya.n@intel.com>,
	"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>,
	"andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>,
	"cujomalainey@chromium.org" <cujomalainey@chromium.org>,
	"Gopal, Vamshi Krishna" <vamshi.krishna.gopal@intel.com>
Subject: RE: [PATCH 03/13] ASoC: Intel: Remove rt5640 support for baytrail solution
Date: Mon, 5 Oct 2020 17:25:26 +0000	[thread overview]
Message-ID: <ca16b4920db44e0789d2786634531df2@intel.com> (raw)
In-Reply-To: <20201005164041.GA29181@sirena.org.uk>

On 2020-10-05 6:40 PM, Mark Brown wrote:
> On Sun, Oct 04, 2020 at 12:01:18PM +0200, Cezary Rojewski wrote:
>> byt-rt5640 is deprecated in favor of bytcr_rt5640 used by
>> sound/soc/intel/atom and SOF solutions both. Remove redundant machine
>> board and all related code.
> 
> This doesn't apply against current code, please check and resend.
> 

Hmm, not seeing any problems when applying these 13 patches on
broonie/sound branch: for-next on my end.

For for-5.10 branch, I see that 'git am' failed on:
PATCH 04/13 ASoC: Intel: Remove baytrail solution
i.e. couldn't find sst-baytrail-pcm.c node (probably changed in between)
but this is certainly not the 04/13 patch.

What am I missing?

Thanks,
Czarek


  reply	other threads:[~2020-10-05 19:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04 10:01 [PATCH 00/13] ASoC: Intel: Remove obsolete solutions and Cezary Rojewski
2020-10-04 10:01 ` [PATCH 01/13] ASoC: Intel: Remove haswell solution Cezary Rojewski
2020-10-04 10:01 ` [PATCH 02/13] ASoC: Intel: Remove max98090 support for baytrail solution Cezary Rojewski
2020-10-04 10:01 ` [PATCH 03/13] ASoC: Intel: Remove rt5640 " Cezary Rojewski
2020-10-05 16:40   ` Mark Brown
2020-10-05 17:25     ` Rojewski, Cezary [this message]
2020-10-05 20:39       ` Mark Brown
2020-10-04 10:01 ` [PATCH 04/13] ASoC: Intel: Remove " Cezary Rojewski
2020-10-04 10:01 ` [PATCH 05/13] ASoC: Intel: Remove SST ACPI component Cezary Rojewski
2020-10-04 10:01 ` [PATCH 06/13] ASoC: Intel: Remove SST firmware components Cezary Rojewski
2020-10-04 10:01 ` [PATCH 07/13] ASoC: Intel: Skylake: Unassign ram_read and read_write ops Cezary Rojewski
2020-10-04 10:01 ` [PATCH 08/13] ASoC: Intel: Remove unused DSP operations Cezary Rojewski
2020-10-04 10:01 ` [PATCH 09/13] ASoC: Intel: Remove unused DSP interface fields Cezary Rojewski
2020-10-04 10:01 ` [PATCH 10/13] ASoC: Intel: Remove SST-legacy specific constants Cezary Rojewski
2020-10-04 10:01 ` [PATCH 11/13] ASoC: Intel: Make atom components independent of sst-dsp Cezary Rojewski
2020-10-04 10:01 ` [PATCH 12/13] ASoC: Intel: Remove sst_pdata structure Cezary Rojewski
2020-10-04 10:01 ` [PATCH 13/13] ASoC: Intel: Remove sst_dsp_get_thread_context Cezary Rojewski
2020-10-05  9:41 ` [PATCH 00/13] ASoC: Intel: Remove obsolete solutions and Andy Shevchenko
2020-10-05 15:05 ` Pierre-Louis Bossart
2020-10-06 15:20 ` 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=ca16b4920db44e0789d2786634531df2@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=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.