From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
Ben Peddell <klightspeed@killerwolves.net>,
Jason Cooper <jason@lakedaemon.net>,
pawel.moll@arm.com, devicetree@vger.kernel.org,
Ian Campbell <ijc@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH 4/4] ARM: Kirkwood: Add support for many Synology NAS devices
Date: Thu, 06 Feb 2014 17:38:28 +0100 [thread overview]
Message-ID: <107057891.kz6j7UkZNk@wuerfel> (raw)
In-Reply-To: <20140206160126.GH29860@lunn.ch>
On Thursday 06 February 2014 17:01:26 Andrew Lunn wrote:
> , but this is, imho,
> > over-fragmenting. I'm sure there's a reason you chose this path, but
> > you haven't explained why in your commit log. So I'm left guessing...
>
> Synology seem to build there devices like lego. They have two
> different RTC blocks. They have three different fan alarm blocks, four
> different led blocks, etc. And to build a product, the just select a
> group of blocks and put them together.
I guess the Armada-370 and newer based ds213j and dsx14 will also be
able to reuse some of the blocks, right?
Arnd
next prev parent reply other threads:[~2014-02-06 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391634309-3123-1-git-send-email-andrew@lunn.ch>
[not found] ` <1391634309-3123-3-git-send-email-andrew@lunn.ch>
[not found] ` <1391634309-3123-3-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 15:19 ` [PATCH 2/4] DT: Vendor prefixes: Add ricoh, ssi and synology Jason Cooper
[not found] ` <1391634309-3123-4-git-send-email-andrew@lunn.ch>
[not found] ` <1391634309-3123-4-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 15:21 ` [PATCH 3/4] DT: i2c: Trivial: Add sii,s35390a Jason Cooper
[not found] ` <1391634309-3123-5-git-send-email-andrew@lunn.ch>
2014-02-06 15:39 ` [PATCH 4/4] ARM: Kirkwood: Add support for many Synology NAS devices Jason Cooper
2014-02-06 16:01 ` Andrew Lunn
2014-02-06 16:38 ` Arnd Bergmann [this message]
2014-02-06 17:03 ` Andrew Lunn
[not found] ` <20140206170333.GK29860-g2DYL2Zd6BY@public.gmane.org>
2014-02-06 17:26 ` Jason Cooper
[not found] ` <20140206160126.GH29860-g2DYL2Zd6BY@public.gmane.org>
2014-02-07 7:44 ` Ben Peddell
2014-02-10 11:41 ` Ian Campbell
2014-02-06 16:39 ` Ian Campbell
[not found] ` <1391704765.2162.7.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-02-06 16:50 ` Andrew Lunn
2014-02-06 16:52 ` Ian Campbell
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=107057891.kz6j7UkZNk@wuerfel \
--to=arnd@arndb.de \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=klightspeed@killerwolves.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.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