From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753970Ab3AKJgt (ORCPT ); Fri, 11 Jan 2013 04:36:49 -0500 Received: from fw-tnat.cambridge.arm.com ([217.140.96.21]:49056 "EHLO cam-smtp0.cambridge.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751591Ab3AKJgq (ORCPT ); Fri, 11 Jan 2013 04:36:46 -0500 Date: Fri, 11 Jan 2013 09:36:02 +0000 From: Catalin Marinas To: Stephen Rothwell Cc: Al Viro , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Will Deacon Subject: Re: linux-next: manual merge of the signal tree with the arm64 tree Message-ID: <20130111093602.GB13405@arm.com> References: <20130111154617.cab6a8d1ff13a4f200969b9d@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130111154617.cab6a8d1ff13a4f200969b9d@canb.auug.org.au> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Fri, Jan 11, 2013 at 04:46:17AM +0000, Stephen Rothwell wrote: > Today's linux-next merge of the signal tree got a conflict in > arch/arm64/kernel/signal32.c between commits 068f1bb36cf1 ("arm64: > compat: include sa_restorer in old action from rt_sigaction") and > efed4d52e39f ("arm64: compat: ensure access_ok checks are performed on > user structures") from the arm64 tree and various commits from the signal > tree. > > The latter removes the code modified by the former, so I did that. I think the fix is fine. I'll give Al's patches a test and I can probably drop Will's patches. Thanks. -- Catalin