linux-kernel - linux-next: manual merge of the signal tree with the mips 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: <20130102141116.a93c916fe9f20110a4ca668c@canb.auug.org.au>
Date:	Wed, 2 Jan 2013 14:11:16 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ralf Baechle <ralf@...ux-mips.org>
Subject: linux-next: manual merge of the signal tree with the mips tree

Hi Al,

Today's linux-next merge of the signal tree got a conflict in
arch/mips/kernel/syscall.c between commit 12890d0f61fc ("MIPS: sysmips:
Rewrite to use SYSCALL_DEFINE3()") from the mips tree and commit
cc524ca3714b ("mips: kill sysmips() wrapper, switch to SYSCALL_DEFINE")
from the signal tree.

These patches are doing the same thing. I fixed it up (using the mips
tree version, which no longer passes regs to mips_atomic_set()) 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