From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] SOCFPGA driver updates for 3.18
Date: Tue, 09 Sep 2014 16:59:07 +0200 [thread overview]
Message-ID: <3081326.KgOEtsBgKv@wuerfel> (raw)
In-Reply-To: <1409847105-27241-2-git-send-email-dinguyen@opensource.altera.com>
On Thursday 04 September 2014 11:11:45 dinguyen at opensource.altera.com wrote:
> Hi Arnd, Kevin and Olof,
>
> Please consider pulling this patch for v3.18. Boris had given me permission to
> take this patch together with it's DTS component. The DTS portion was in the
> previous pull request.
I have no objections to the code, but I don't understand what you gain
from merging it through arm-soc. There is no dependency between the
driver and the dts entries in any way, you just need to have both in order
for things to work.
We can always pull in drivers with permission from the maintainer when there
is a good reason to do that, but I don't see that reason for this patch,
so I'd prefer to have Boris merge it through his tree, unless I'm missing
something.
Arnd
next prev parent reply other threads:[~2014-09-09 14:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 16:11 [GIT PULL 1/2] SOCFPGA updates for 3.18 dinguyen at opensource.altera.com
2014-09-04 16:11 ` [GIT PULL 2/2] SOCFPGA driver " dinguyen at opensource.altera.com
2014-09-09 14:59 ` Arnd Bergmann [this message]
2014-09-09 15:45 ` Borislav Petkov
2014-09-09 15:53 ` Arnd Bergmann
2014-09-09 18:40 ` Borislav Petkov
2014-09-09 14:17 ` [GIT PULL 1/2] SOCFPGA " Pavel Machek
2014-09-09 15:02 ` Arnd Bergmann
2014-09-09 21:02 ` Pavel Machek
2014-09-10 7:13 ` Ulf Hansson
2014-09-10 8:33 ` Pavel Machek
2014-09-10 10:42 ` Ulf Hansson
2014-09-10 11:00 ` Pavel Machek
2014-09-10 14:19 ` Dinh Nguyen
2014-09-10 14:36 ` Marek Vasut
2014-09-09 14:55 ` Arnd Bergmann
2014-09-09 16:04 ` Dinh Nguyen
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=3081326.KgOEtsBgKv@wuerfel \
--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