linux-kernel - linux-next: manual merge of the msm tree with the arm-soc tree

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>] [day] [month] [year] [list]

Message-Id: <20130625174152.d776ac051f6f19dfbf876634@canb.auug.org.au>
Date:	Tue, 25 Jun 2013 17:41:52 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	David Brown <davidb@...eaurora.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Chen Gang <gang.chen@...anux.com>,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	<linux-arm-kernel@...ts.infradead.org>,
	Stephen Boyd <sboyd@...eaurora.org>
Subject: linux-next: manual merge of the msm tree with the arm-soc tree

Hi David,

Today's linux-next merge of the msm tree got a conflict in
arch/arm/mach-msm/clock-debug.c between commit ad8c373c9aa3 ("arch: arm:
mach-msm: using strlcpy instead of strncpy") from the arm-soc tree and
commit 8cc7f5338e72 ("ARM: msm: Migrate to common clock framework") from
the msm tree.

The latter removed the file, so I did that, and can carry the fix as
necessary (no action is required).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped