From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754917Ab2CNE7F (ORCPT ); Wed, 14 Mar 2012 00:59:05 -0400 Received: from e5.ny.us.ibm.com ([32.97.182.145]:38665 "EHLO e5.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753208Ab2CNE7C (ORCPT ); Wed, 14 Mar 2012 00:59:02 -0400 Date: Wed, 14 Mar 2012 10:25:44 +0530 From: Srikar Dronamraju To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Subject: Re: linux-next: manual merge of the uprobes tree with the tip tree Message-ID: <20120314045544.GA4644@linux.vnet.ibm.com> Reply-To: Srikar Dronamraju References: <20120314151444.a34eef495739e13506ac5b1a@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20120314151444.a34eef495739e13506ac5b1a@canb.auug.org.au> User-Agent: Mutt/1.5.20 (2009-06-14) X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12031404-5930-0000-0000-00000615484E Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The linux-next merge of the uprobes tree gets several conflicts against > the tip tree because the same patches appear in both threes and there are > further changes to some files in the uprobes tree. > > Merging uprobes/for-next (1fe509b uprobes/core: Handle breakpoint and singlestep exception.) > CONFLICT (add/add): Merge conflict in kernel/events/uprobes.c > CONFLICT (content): Merge conflict in kernel/events/Makefile > CONFLICT (add/add): Merge conflict in include/linux/uprobes.h > CONFLICT (add/add): Merge conflict in arch/x86/kernel/uprobes.c > CONFLICT (add/add): Merge conflict in arch/x86/include/asm/uprobes.h > > The easiest way to remove these conflicts would be for you to rebase the > uprobes tree onto the perl/uprobes branch of the tip tree (I assume that > all the uprobes code will eventually be merged to Linus via the tip tree) > or a subset of that branch that is the common set of patches. Okay, I will go with this suggestion. Infact this is actually easier for me. -- Thanks and Regards Srikar