From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Nicolas Kaiser <nikai@nikai.net>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] video/omap: remove mux.h include
Date: Tue, 05 Oct 2010 10:02:22 +0000 [thread overview]
Message-ID: <1286272942.2358.29.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <20101004203842.088b0cb2@absol.kitzblitz>
On Mon, 2010-10-04 at 20:38 +0200, ext Nicolas Kaiser wrote:
> Including mux.h should no longer be needed for omap2/3/4 SoCs
> outside arch/arm/mach-omap2 files.
>
> Signed-off-by: Nicolas Kaiser <nikai@nikai.net>
Thanks, applied to my tree.
Tomi
prev parent reply other threads:[~2010-10-05 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 15:43 [PATCH] video/omap: remove duplicated include Nicolas Kaiser
2010-10-04 17:54 ` Tony Lindgren
2010-10-04 18:38 ` [PATCH] video/omap: remove mux.h include Nicolas Kaiser
2010-10-04 18:47 ` Tony Lindgren
2010-10-05 10:02 ` Tomi Valkeinen [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=1286272942.2358.29.camel@tubuntu.research.nokia.com \
--to=tomi.valkeinen@nokia.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nikai@nikai.net \
--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).