All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
	tiwai@suse.de, alsa-devel@alsa-project.org,
	pierre-louis.bossart@linux.intel.com, bard.liao@intel.com,
	peter.ujfalusi@linux.intel.com,
	ranjani.sridharan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ASoC/soundwire: remove is_sdca boolean property
Date: Wed, 23 Nov 2022 22:46:17 +0530	[thread overview]
Message-ID: <Y35VYW/s8Cnv1jEV@matsya> (raw)
In-Reply-To: <Y347f24Tx5yZtjLw@sirena.org.uk>

On 23-11-22, 15:25, Mark Brown wrote:
> On Wed, Nov 23, 2022 at 08:22:14PM +0530, Vinod Koul wrote:
> > On 18-11-22, 15:39, Mark Brown wrote:
> > > On Fri, Nov 18, 2022 at 10:58:06AM +0800, Bard Liao wrote:
> > > > From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> 
> > > > The Device_ID registers already tell us if a device supports the SDCA
> > > > specification or not, in hindsight we never needed a property when the
> > > > information is reported by both hardware and ACPI.
> 
> > > Acked-by: Mark Brown <broonie@kernel.org>
> 
> > sound/soc/codecs/rt1318-sdw.c does not exist for me in sdw/next. Can I
> > get a tag for the changes merged into ASoC for this
> 
> Not reasonably, that's basically the entire tree since Linus doesn't
> like branches.

Okay.

Anyway we are close to merge window, lets postpone this after that

Thanks
-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	tiwai@suse.de, Bard Liao <yung-chuan.liao@linux.intel.com>,
	pierre-louis.bossart@linux.intel.com,
	ranjani.sridharan@linux.intel.com,
	peter.ujfalusi@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 1/2] ASoC/soundwire: remove is_sdca boolean property
Date: Wed, 23 Nov 2022 22:46:17 +0530	[thread overview]
Message-ID: <Y35VYW/s8Cnv1jEV@matsya> (raw)
In-Reply-To: <Y347f24Tx5yZtjLw@sirena.org.uk>

On 23-11-22, 15:25, Mark Brown wrote:
> On Wed, Nov 23, 2022 at 08:22:14PM +0530, Vinod Koul wrote:
> > On 18-11-22, 15:39, Mark Brown wrote:
> > > On Fri, Nov 18, 2022 at 10:58:06AM +0800, Bard Liao wrote:
> > > > From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> 
> > > > The Device_ID registers already tell us if a device supports the SDCA
> > > > specification or not, in hindsight we never needed a property when the
> > > > information is reported by both hardware and ACPI.
> 
> > > Acked-by: Mark Brown <broonie@kernel.org>
> 
> > sound/soc/codecs/rt1318-sdw.c does not exist for me in sdw/next. Can I
> > get a tag for the changes merged into ASoC for this
> 
> Not reasonably, that's basically the entire tree since Linus doesn't
> like branches.

Okay.

Anyway we are close to merge window, lets postpone this after that

Thanks
-- 
~Vinod

  reply	other threads:[~2022-11-23 17:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  2:58 [PATCH v2 0/2] ASoC/soundwire: revisit support for clock registers Bard Liao
2022-11-18  2:58 ` Bard Liao
2022-11-18  2:58 ` [PATCH v2 1/2] ASoC/soundwire: remove is_sdca boolean property Bard Liao
2022-11-18  2:58   ` Bard Liao
2022-11-18 15:39   ` Mark Brown
2022-11-18 15:39     ` Mark Brown
2022-11-23 14:52     ` Vinod Koul
2022-11-23 14:52       ` Vinod Koul
2022-11-23 15:25       ` Mark Brown
2022-11-23 15:25         ` Mark Brown
2022-11-23 17:16         ` Vinod Koul [this message]
2022-11-23 17:16           ` Vinod Koul
2022-11-23  9:33   ` Charles Keepax
2022-11-23  9:33     ` Charles Keepax
2022-11-18  2:58 ` [PATCH v2 2/2] soundwire: enable optional clock registers for SoundWire 1.2 devices Bard Liao
2022-11-18  2:58   ` Bard Liao
2022-11-23  9:33   ` Charles Keepax
2022-11-23  9:33     ` Charles Keepax
2023-01-09 16:08 ` [PATCH v2 0/2] ASoC/soundwire: revisit support for clock registers Vinod Koul
2023-01-09 16:08   ` Vinod Koul

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=Y35VYW/s8Cnv1jEV@matsya \
    --to=vkoul@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@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 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.