From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SoCFPGA DTS updates for v4.4
Date: Tue, 06 Oct 2015 16:34:10 +0200 [thread overview]
Message-ID: <6510812.tHLFEUGyjH@wuerfel> (raw)
In-Reply-To: <1444125744-21798-1-git-send-email-dinguyen@opensource.altera.com>
On Tuesday 06 October 2015 05:02:24 dinguyen at opensource.altera.com wrote:
> Hi Arnd, Kevin, and Olof,
>
> Please consider pulling these patches for v4.4. For the arm64 patch, I don't
> have an official ACK from the DTS guys, but I did get an "its looks okay"
> with a condition that I fix up the ranges property for /soc node.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/372136.html
>
>
Looks ok, merged into next/dt now.
I see one commit for the defconfig file. We normally put those into a separate
branch with just defconfig changes, to avoid merge conflicts, but it doesn't
seem worth to make you redo the pull request for that. Please do that next
time though.
Arnd
prev parent reply other threads:[~2015-10-06 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:02 [GIT PULL] SoCFPGA DTS updates for v4.4 dinguyen at opensource.altera.com
2015-10-06 14:34 ` 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=6510812.tHLFEUGyjH@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