All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
	"patches@opensource.wolfsonmicro.com"
	<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: Rename WM8915 to WM8996
Date: Wed, 29 Jun 2011 10:31:15 +0100	[thread overview]
Message-ID: <4E0AF0E3.2060708@ti.com> (raw)
In-Reply-To: <07ce01cc362e$7fac3710$7f04a530$%kim@samsung.com>

On 29/06/11 08:30, Kukjin Kim wrote:
> Mark Brown wrote:
>>
>> For marketing reasons the part will be called WM8996. In order to avoid
>> user confusion rename the driver to reflect this.
>>
>> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>> ---
>>
>> The cross tree issues make this difficult to merge as there's
>> dependencies in both ASoC and Samsung trees - Kukjin, would you be OK
>> with merging this via ALSA late on in the merge window after both
>> Samsung and ASoC trees have merged?
>>
> Yes, it's ok to me :)
> 
> As a note, basically my tree will be sent to upstream via rmk during merge
> window so I'm not sure when it is merged.
> 
>> I will have a go at constructing some branches which do the right thing
>> and can be merged now (so a base rename patch then a merge of that into
>> ASoC which deals with all the work that has been done in the driver this
>> release cycle) but I wanted to get this first option out there now.
>>
>>  arch/arm/mach-s3c64xx/mach-crag6410.c |   18 +-
> 
> If required,
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
> 

Acked-by: Liam Girdwood <lrg@ti.com>

      reply	other threads:[~2011-06-29  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1309317832-24241-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2011-06-29  7:30 ` [PATCH] ASoC: Rename WM8915 to WM8996 Kukjin Kim
2011-06-29  9:31   ` Liam Girdwood [this message]

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=4E0AF0E3.2060708@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kgene.kim@samsung.com \
    --cc=patches@opensource.wolfsonmicro.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.