From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
lrg@ti.com, s-guiriec@ti.com
Subject: Re: [PATCH 3/3] ASoC: OMAP: HDMI: Obtain DMA port from resources
Date: Thu, 15 Nov 2012 13:10:17 +0900 [thread overview]
Message-ID: <20121115040141.GC7599@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50A45467.6070404@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 1334 bytes --]
On Wed, Nov 14, 2012 at 08:33:11PM -0600, Ricardo Neri wrote:
> On 11/14/2012 05:08 PM, Mark Brown wrote:
> >Don't do this. With a change like this which must be made at the same
> >time over multiple subsystems it is very important that you send all the
> but the changes will hit linux-next at some point and they could be
> tested there, right?
This isn't much fun for anyone doing git bisect, it means the device
will be unusuable for large periods of history.
> Sorry, as changes for the HDMI drivers go to several maintainers, I
> was trying to send the relevant patches to the respective
> maintainers and avoid potential merge/rebase issues.
You need to make sure everyone involved knows what's going on - review
should really turn up the sort of issue I just highlighted.
> Tomi has already taken the DSS changes. Perhaps, if you and Tomi
> agree, Tomi could also take the ASoC and the arch/arm/mach-omap2
> changes. This way all changes come from the same tree.
Yes, we're going to need to do that. Ideally all the changes would be
squashed into a single commit.
> >>This change should be present in K3.8.
> >What is "K3.8"?
> I meant that Tomi took the DSS changes in [1] on his master branch
> and he should push them upstream when the merge window for kernel
> v3.8 opens.
Do you mean that "K3.8" is "v3.8"?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-15 4:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 2:30 [PATCH 0/3] Updated names for ASoC OMAP HDMI drivers Ricardo Neri
2012-11-14 2:30 ` [PATCH 1/3] ASoC: OMAP: HDMI: Update machine driver name Ricardo Neri
2012-11-14 10:16 ` Liam Girdwood
2012-11-14 17:00 ` Ricardo Neri
2012-11-14 2:30 ` [PATCH 2/3] ASoC: OMAP: HDMI: Update CPU DAI " Ricardo Neri
2012-11-14 2:30 ` [PATCH 3/3] ASoC: OMAP: HDMI: Obtain DMA port from resources Ricardo Neri
2012-11-14 3:27 ` Mark Brown
2012-11-14 17:07 ` Ricardo Neri
2012-11-14 23:08 ` Mark Brown
2012-11-15 2:33 ` Ricardo Neri
2012-11-15 4:10 ` Mark Brown [this message]
2012-11-15 16:22 ` Ricardo Neri
2012-11-15 9:45 ` Tomi Valkeinen
2012-11-15 12:36 ` Tomi Valkeinen
2012-11-16 1:39 ` Ricardo Neri
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=20121115040141.GC7599@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.com \
--cc=tomi.valkeinen@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.