From: Michael Walle <michael-QKn5cuLxLXY@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 9/9] Kirkwood: Add basic device tree support for QNAP TS219.
Date: Sun, 10 Jun 2012 23:22:01 +0200 [thread overview]
Message-ID: <201206102322.01981.michael@walle.cc> (raw)
In-Reply-To: <1339324322-29388-10-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
Am Sonntag 10 Juni 2012, 12:32:01 schrieb Andrew Lunn:
[..]
> +config MACH_TS219_DT
> + bool "Device Tree for QNAP TS-110, TS-119, TS-119P+, TS-210, TS-219,
> TS-219P and TS-219P+ Turbo NAS" + select ARCH_KIRKWOOD_DT
> + select ARM_APPENDED_DTB
> + select ARM_ATAG_DTB_COMPAT
> + help
> + Say 'Y' here if you want your kernel to support the QNAP
> + TS-110, TS-119, TS-119P+, TS-210, TS-219, TS-219P and
> + TS-219P+ Turbo NAS devices using Fattened Device Tree.
> + There are two different Device Tree descriptions, depending
> + on if the device is based on an if the board uses the MV6281
> + or MV6282. If you have the wrong one, the buttons will not
> + work.
> +
whitespace errors above
--
Michael
prev parent reply other threads:[~2012-06-10 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 10:32 [PATCH 9/9] Kirkwood: Add basic device tree support for QNAP TS219 Andrew Lunn
[not found] ` <1339324322-29388-10-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2012-06-10 17:23 ` Jason Cooper
2012-06-10 21:22 ` Michael Walle [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=201206102322.01981.michael@walle.cc \
--to=michael-qkn5culxlxy@public.gmane.org \
--cc=andrew-g2DYL2Zd6BY@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).