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 driver-core.current tree Date: Tue, 18 Jun 2013 22:55:00 -0700 Message-ID: <20130619055500.GA5283@kroah.com> References: <20130619153225.9ff68f0984bfa54333c4df10@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:38706 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751089Ab3FSFyV (ORCPT ); Wed, 19 Jun 2013 01:54:21 -0400 Content-Disposition: inline In-Reply-To: <20130619153225.9ff68f0984bfa54333c4df10@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Ming Lei , Takashi Iwai On Wed, Jun 19, 2013 at 03:32:25PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in > drivers/base/firmware_class.c between commit 875979368eb4 ("firmware > loader: fix use-after-free by double abort") from the driver-core.current > tree and commit fe304143b0c3 ("firmware: Avoid deadlock of usermodehelper > lock at shutdown") from the driver-core tree. > > I fixed it up (more may be required - see below) and can carry the fix as > necessary (no action is required). Thanks, the merge looks correct, Ming, any objection? greg k-h