From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: vt8500: Fixup for missing gpio.h
Date: Sun, 30 Sep 2012 12:00:42 +0000 [thread overview]
Message-ID: <201209301200.43031.arnd@arndb.de> (raw)
In-Reply-To: <20120929211805.GF12999@quad.lixom.net>
On Saturday 29 September 2012, Olof Johansson wrote:
> By the way, I noticed that there is no VT8500 defconfig in the tree, so there's
> no easy way for us to check for build breakages of your platform. You might
> want to add one.
I suppose if Tony and the other vt8500 developers manage to get the platform
enabled for CONFIG_MULTIPLATFORM in 3.8, we can simply enable it in a future
multi_v5_defconfig and don't even need the specific one.
On the other hand, those systems are fairly resource limited, so maybe
we want to do both after all.
Arnd
prev parent reply other threads:[~2012-09-30 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 17:47 [PATCH] Fixup for v3.7 Tony Prisk
2012-09-25 17:47 ` [PATCH] arm: vt8500: Fixup for missing gpio.h Tony Prisk
2012-09-29 21:18 ` Olof Johansson
2012-09-29 21:58 ` Tony Prisk
2012-09-30 12:00 ` Arnd Bergmann [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=201209301200.43031.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).