From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753145AbdKAGER (ORCPT ); Wed, 1 Nov 2017 02:04:17 -0400 Received: from ozlabs.org ([103.22.144.67]:43009 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750973AbdKAGEP (ORCPT ); Wed, 1 Nov 2017 02:04:15 -0400 Date: Wed, 1 Nov 2017 17:04:13 +1100 From: Stephen Rothwell To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Mark Rutland Subject: linux-next: manual merge of the tip tree with the s390 tree Message-ID: <20171101170413.7d06a1c1@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/s390/lib/spinlock.c between commit: eb3b7b848fb3 ("s390/rwlock: introduce rwlock wait queueing") (at least) from the s390 tree and commit: 6aa7de059173 ("locking/atomics: COCCINELLE/treewide: Convert trivial ACCESS_ONCE() patterns to READ_ONCE()/WRITE_ONCE()") from the tip tree. I fixed it up (the ACCESS_ONCE instances replaced in the latter were removed by the former ... there was one more ACCESS_ONCE added, but I left it in place) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell