From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753083AbbG0F0o (ORCPT ); Mon, 27 Jul 2015 01:26:44 -0400 Received: from ozlabs.org ([103.22.144.67]:55632 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752127AbbG0F0n (ORCPT ); Mon, 27 Jul 2015 01:26:43 -0400 Date: Mon, 27 Jul 2015 15:26:41 +1000 From: Stephen Rothwell To: Andrew Morton Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, "Kirill A. Shutemov" , Ingo Molnar , Dave Hansen , Oleg Nesterov Subject: linux-next: manual merge of the akpm tree with Linus' tree Message-ID: <20150727152641.1959de99@canb.auug.org.au> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; i586-pc-linux-gnu) 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 Andrew, Today's linux-next merge of the akpm tree got a conflict in: arch/x86/mm/mpx.c between commit: a89652769470 ("x86/mpx: Do not set ->vm_ops on MPX VMAs") from Linus' tree and patch: "mm, mpx: add "vm_flags_t vm_flags" arg to do_mmap_pgoff()" from the akpm tree. I fixed it up (I used the akpm tree version of mpx_map()) and can carry the fix as necessary (no action is required). -- Cheers, Stephen Rothwell sfr@canb.auug.org.au