From: Ralf Baechle <ralf@linux-mips.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] video/logo: Remove MIPS-specific include section
Date: Mon, 04 Nov 2013 17:13:27 +0000 [thread overview]
Message-ID: <20131104171327.GS1615@linux-mips.org> (raw)
In-Reply-To: <1383554550-20901-1-git-send-email-geert@linux-m68k.org>
On Mon, Nov 04, 2013 at 09:42:30AM +0100, Geert Uytterhoeven wrote:
> Since commit 41702d9a4fffa9e25b2ad9d4af09b3013fa155e1 ("logo.c: get rid of
> mips_machgroup") there's no longer a need to include <asm/bootinfo.h> on
> MIPS.
Yes,
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Generally CONFIG_<ARCH> should probably be considered a bug even if only
it's used to hide crap like this.
Ralf
next prev parent reply other threads:[~2013-11-04 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 8:42 [PATCH] video/logo: Remove MIPS-specific include section Geert Uytterhoeven
2013-11-04 17:13 ` Ralf Baechle [this message]
2014-01-10 11:56 ` Tomi Valkeinen
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=20131104171327.GS1615@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=plagnioj@jcrosoft.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 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).