From: avictor.za@gmail.com (Andrew Victor)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] AT91: taskit PortuxG20 and Stamp9G20 board support
Date: Tue, 13 Apr 2010 10:25:14 +0200 [thread overview]
Message-ID: <v2qcd73a99e1004130125y5daef203n241dfc130f7dcfb9@mail.gmail.com> (raw)
In-Reply-To: <1268916069-21639-1-git-send-email-christian.glindkamp@taskit.de>
hi Christian,
> Both boards share the same board file, as the PortuxG20 is basically an
> SBC based on the Stamp9G20.
> +config MACH_PORTUXG20
> + ? ? ? bool "taskit PortuxG20"
> + ? ? ? depends on ARCH_AT91SAM9G20
> + ? ? ? help
> + ? ? ? ? Select this if you are using taskit's PortuxG20.
> + ? ? ? ? <http://www.taskit.de/en/>
> +
> +config MACH_STAMP9G20
> + ? ? ? bool "taskit Stamp9G20 CPU module"
> + ? ? ? depends on ARCH_AT91SAM9G20
> + ? ? ? help
> + ? ? ? ? Select this if you are using taskit's Stamp9G20 CPU module on its
> + ? ? ? ? evaluation board.
> + ? ? ? ? <http://www.taskit.de/en/>
Please remove the "depends on ARCH_AT91SAM9G20" lines.
These configuration options are in an "if ARCH_AT91SAM9G20" section,
so the "depends on" are no longer needed.
Otherwise, the patches looks fine.
Acked-by: Andrew Victor <linux@maxim.org.za>
Please submit the patches to Russell King's patch-tracking system.
Thanks.
Regards,
Andrew Victor
next prev parent reply other threads:[~2010-04-13 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 11:40 [PATCH 0/2] Support for taskit AT91SAM9G20 boards Christian Glindkamp
2010-03-18 11:40 ` [PATCH 1/2] AT91: taskit PortuxG20 and Stamp9G20 board support Christian Glindkamp
2010-03-18 11:53 ` Russell King - ARM Linux
2010-03-18 12:41 ` [PATCH 1/2 v2] " Christian Glindkamp
2010-04-13 8:25 ` Andrew Victor [this message]
2010-03-18 11:40 ` [PATCH 2/2] AT91: add defconfig for taskit PortuxG20 and Stamp9G20 Christian Glindkamp
2010-04-12 8:18 ` [PATCH 0/2] Support for taskit AT91SAM9G20 boards Christian Glindkamp
2010-04-12 8:27 ` Russell King - ARM Linux
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=v2qcd73a99e1004130125y5daef203n241dfc130f7dcfb9@mail.gmail.com \
--to=avictor.za@gmail.com \
--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).