linux-kernel - Re: [GIT PULL] ARM: arm-soc fixes for 3.8

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]

Message-ID: <20121220151059.GU4989@atomide.com>
Date:	Thu, 20 Dec 2012 07:10:59 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:	Olof Johansson <olof@...om.net>, arm@...nel.org,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Russell King - ARM Linux <linux@....linux.org.uk>
Subject: Re: [GIT PULL] ARM: arm-soc fixes for 3.8

* Maxime Ripard <maxime.ripard@...e-electrons.com> [121218 07:08]:
> Hi Olof,
> 
> Le 18/12/2012 07:55, Olof Johansson a écrit :
> > Maxime Ripard (1):
> >       ARM: sunxi: Change device tree naming scheme for sunxi
> 
> There's something odd about this one (commit 68136b10). The patch that
> you seem to have applied differs from the one I sent. The DTs files
> appears to have not been renamed, while in the patch I sent
> (http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137105.html),
> it's the case.
> 
> Do you know what happened here? What can we do to fix that?

Looks like that's trivial to fix as needed, no need to rebuild
the branch to fix that AFAIK.

The fix can be done once Olof is available online again.

Linus, I suggest that you go ahead and pull this if there are
no other issues with this branch.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/