From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 2/2] ASoC: tegra: complete Tegra->Tegra20 renaming
Date: Fri, 06 Apr 2012 09:44:16 -0600 [thread overview]
Message-ID: <4F7F0F50.8070205@wwwdotorg.org> (raw)
In-Reply-To: <20120406132324.GD19424@opensource.wolfsonmicro.com>
On 04/06/2012 07:23 AM, Mark Brown wrote:
> On Thu, Apr 05, 2012 at 03:54:54PM -0600, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Rename Tegra20-specific Kconfig variables, module filenames, all internal
>> symbol names, clocks, and platform devices, to reflect the fact the DAS
>> and I2S drivers are for a specific HW version.
>
> Oops, sorry - replied to the wrong one - this one doesn't seem to apply
> against for-3.5, I applied 1/2 though. I believe this is due to 3.4
> fixes not having propagated over 3.5 yet. Can you regenerate against
> for-3.5 please, or perhaps it's best to wait until things have merged
> back up?
Yes, it's because of the I2S debugfs fix.
I'm not sure when "things have merged back up" will be; do you intend to
merge your for-3.4 branch into for-3.5 at any particular time, or
perhaps rebase your for-3.5 onto v3.4-rc2 when its out?
Alternatively, I can regenerate that patch against your for-3.5, but
then you'll get a merge conflict when merging in your for-3.4, since the
code it affects will have experienced a rename. Should be trivial to
resolve though.
next prev parent reply other threads:[~2012-04-06 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 21:54 [PATCH 1/2] ASoC: tegra: rename Tegra20-specific driver files Stephen Warren
[not found] ` <1333662894-22672-2-git-send-email-swarren@wwwdotorg.org>
2012-04-06 13:18 ` [PATCH 2/2] ASoC: tegra: complete Tegra->Tegra20 renaming Mark Brown
2012-04-06 13:23 ` Mark Brown
2012-04-06 15:44 ` Stephen Warren [this message]
2012-04-06 15:46 ` 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=4F7F0F50.8070205@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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.