From: Ian Campbell <ijc@hellion.org.uk>
To: Mark Rutland <mark.rutland@arm.com>, arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Eric Anholt <eric@anholt.net>,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Gerd Hoffmann <kraxel@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: dts: Remove use of skeleton.dtsi from bcm283x.dtsi
Date: Tue, 09 Aug 2016 11:48:29 +0100 [thread overview]
Message-ID: <1470739709.4745.23.camel@hellion.org.uk> (raw)
In-Reply-To: <20160803144858.GA29054@leverpostej>
On Wed, 2016-08-03 at 15:48 +0100, Mark Rutland wrote:
>
> > [...]Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
>
> I also don't have the relevant hardware to test with, but this looks
> generally like the right thing. So FWIW:
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks (and Stefan too).
I think these things generally go via the arm-soc tree? Arnd & Olaf,
would it be possible to get this fix in for rc2 please (or in any event
for 4.8). Although it's an external tree I believe build breakage in
the split-out DT git repo is worth addressing.
Ian.
next prev parent reply other threads:[~2016-08-09 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 14:12 [PATCH v2 1/2] ARM: dts: Remove use of skeleton.dtsi from bcm283x.dtsi Ian Campbell
2016-08-03 14:12 ` [PATCH v2 2/2] ARM64: dts: bcm: Use a symlink to R-Pi dtsi files from arch=arm Ian Campbell
2016-08-03 14:54 ` Mark Rutland
2016-08-03 14:48 ` [PATCH v2 1/2] ARM: dts: Remove use of skeleton.dtsi from bcm283x.dtsi Mark Rutland
2016-08-09 10:48 ` Ian Campbell [this message]
2016-08-18 7:21 ` Ian Campbell
2016-08-18 10:23 ` Mark Rutland
2016-08-23 10:09 ` Arnd Bergmann
2016-09-09 14:45 ` Ian Campbell
2016-09-09 15:47 ` Arnd Bergmann
2016-09-09 16:21 ` Ian Campbell
2016-08-03 16:57 ` Stefan Wahren
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=1470739709.4745.23.camel@hellion.org.uk \
--to=ijc@hellion.org.uk \
--cc=arm@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=frowand.list@gmail.com \
--cc=kraxel@redhat.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=will.deacon@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