From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751481AbcCDLOQ (ORCPT ); Fri, 4 Mar 2016 06:14:16 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34057 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbcCDLOO (ORCPT ); Fri, 4 Mar 2016 06:14:14 -0500 Date: Fri, 4 Mar 2016 12:14:09 +0100 From: Ingo Molnar To: Dan Williams Cc: Borislav Petkov , Thomas Gleixner , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , Toshi Kani Subject: Re: [RFC] Using tip.git 'core/resources' as a baseline for a nvdimm.git topic branch Message-ID: <20160304111409.GA17790@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Dan Williams wrote: > I have nvdimm changes that depend on the re-worked region_intersects() > routine that is presently located in -tip. Any objections with me > using that branch as a baseline for an nvdimm.git topic branch? No objections from me! To make it easier for you I just refreshed that branch, to eliminate an upstream conflict, the new base is: bc94b99636dc Merge tag 'v4.5-rc6' into core/resources, to resolve conflict that way you can base your changes on a fairly fresh upstream kernel as well. There are no regressions in tip:core/resources that I'm aware of. Thanks, Ingo