lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 18 Aug 2016 11:23:49 +0100
From:	Mark Rutland <mark.rutland@....com>
To:	Ian Campbell <ijc@...lion.org.uk>
Cc:	arm@...nel.org, devicetree@...r.kernel.org,
	Stephen Warren <swarren@...dotorg.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Lee Jones <lee@...nel.org>, Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org, Eric Anholt <eric@...olt.net>,
	Rob Herring <robh+dt@...nel.org>,
	Gerd Hoffmann <kraxel@...hat.com>,
	Frank Rowand <frowand.list@...il.com>,
	linux-arm-kernel@...ts.infradead.org,
	linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: dts: Remove use of skeleton.dtsi from
 bcm283x.dtsi

On Thu, Aug 18, 2016 at 08:21:56AM +0100, Ian Campbell wrote:
> On Tue, 2016-08-09 at 11:48 +0100, Ian Campbell wrote:
> > On Wed, 2016-08-03 at 15:48 +0100, Mark Rutland wrote:
> > > 
> > > > [...]Signed-off-by: Ian Campbell <ijc@...lion.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@....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.
> 
> This change doesn't appear to be in either v4.8-rc2, Linus' tree nor in
> the arm-soc tree that I can see. So, ping?
> 
> Or am I barking up the wrong tree pointing this patch towards arm-soc
> (via arm@k.o)?

That's the right place.

The best thing to do would be to resend the patch, with all tags
accumulated, with arm-soc, Arnd, and Olof in the To line (rather than
Cc'd), so it's clear they need to action it.

Thanks,
Mark.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ