From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: omap-mcbsp: Fix compilation error due to leftover code
Date: Thu, 6 Sep 2012 07:37:22 +0800 [thread overview]
Message-ID: <20120905233716.GE10580@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <504470B5.20404@ti.com>
On Mon, Sep 03, 2012 at 11:56:21AM +0300, Peter Ujfalusi wrote:
> So how can we resolve this?
> Are you going to rebase or update your 3.7, for-next topic/omap branches on
> mainline so they will contain the mainline patch (d0db84e)?
So, I think I figured out what you're talking about here. Check -next.
Please if you're going to do stuff like this in future:
- Talk about the actual code we've got. It's OK to explain the history
but it's very important to explain the concrete problem - that was
missing from your mails (the closest we got was "compilation problem").
- Discuss changes to what's there, starting off with "let's throw
everything away" doesn't help with clarity especially with a missing
problem description.
The problem description is especially critical.
next prev parent reply other threads:[~2012-09-05 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 14:06 [PATCH] ASoC: omap-mcbsp: Fix compilation error due to leftover code Peter Ujfalusi
2012-08-30 18:02 ` Mark Brown
2012-09-03 8:56 ` Peter Ujfalusi
2012-09-05 23:37 ` Mark Brown [this message]
2012-09-05 4:48 ` Stephen Rothwell
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=20120905233716.GE10580@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sfr@canb.auug.org.au \
/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.