From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tony Lindgren <tony@atomide.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Tim Gardner <tim.gardner@canonical.com>,
Liam Girdwood <lrg@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: [PATCH 3.7-rc1] omap zoom2.c: Fix compile error by including correct header files
Date: Sat, 27 Oct 2012 22:44:26 +0100 [thread overview]
Message-ID: <20121027214421.GG4564@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121003163102.GB4840@atomide.com>
[-- Attachment #1.1: Type: text/plain, Size: 616 bytes --]
On Wed, Oct 03, 2012 at 09:31:02AM -0700, Tony Lindgren wrote:
> Actually we can also drop "#include <mach/hardware.h>" too,
> it's now empty for mach-omap2. I've updated Tim's patch below
> for you guys to queue via the ASoC fixes. It's against the
> current linux next.
Applied. Tim, you should send patches using subject lines appropriate
for the subsystem you're submitting against *especially* if the patch is
to be deferred for some future time as it makes it harder to search for
the patch. If your changelog looks different to the other changelogs
for the thing you're patching that should be a warning.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-10-27 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 14:31 [PATCH 3.7-rc1] omap zoom2.c: Fix compile error by including correct header files Tim Gardner
2012-10-03 14:52 ` Peter Ujfalusi
2012-10-03 15:59 ` Tony Lindgren
2012-10-03 16:31 ` Tony Lindgren
2012-10-27 21:44 ` Mark Brown [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=20121027214421.GG4564@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tim.gardner@canonical.com \
--cc=tiwai@suse.de \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).