From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: manual merge of the driver-core tree with the tip tree Date: Fri, 1 Aug 2014 19:40:38 -0700 Message-ID: <20140802024038.GB22728@kroah.com> References: <20140731170735.5cf2062b@canb.auug.org.au> <20140801002017.GA2945@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Kees Cook Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Linux-Next , LKML , David Riley , John Stultz List-Id: linux-next.vger.kernel.org On Fri, Aug 01, 2014 at 07:38:26PM -0400, Kees Cook wrote: > On Thu, Jul 31, 2014 at 8:20 PM, Greg KH wrote: > > On Thu, Jul 31, 2014 at 05:07:35PM +1000, Stephen Rothwell wrote: > >> Hi Greg, > >> > >> Today's linux-next merge of the driver-core tree got a conflict in > >> lib/Kconfig.debug between commit e704f93af5a0 ("kernel: time: Add > >> udelay_test module to validate udelay") from the tip tree and commit > >> 0a8adf584759 ("test: add firmware_class loader test") from the > >> driver-core tree. > >> > >> I fixed it up (see below) and can carry the fix as necessary (no action > >> is required). > > > > Looks good, thanks. > > For keeping things regularized, could this module instead be named > "test_udelay", to match the rest of most of the test modules? > (Starting with "test_".) Makes sense, want to send a patch to rename it? thanks, greg k-h