From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: manual merge of the staging tree with the staging.current tree Date: Mon, 4 Dec 2017 10:09:44 +0100 Message-ID: <20171204090944.GA16936@kroah.com> References: <20171204125045.59e1a704@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]:36945 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753067AbdLDJJh (ORCPT ); Mon, 4 Dec 2017 04:09:37 -0500 Content-Disposition: inline In-Reply-To: <20171204125045.59e1a704@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Xingyu Chen , Jonathan Cameron , Martin Blumenstingl On Mon, Dec 04, 2017 at 12:50:45PM +1100, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > drivers/iio/adc/meson_saradc.c > > between commit: > > d85eed9f5763 ("iio: adc: meson-saradc: initialize the bandgap correctly on older SoCs") > > from the staging.current tree and commit: > > 930df4d853a8 ("iio: adc: meson-saradc: remove irrelevant clock "sana"") > > from the staging tree. > > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for merging. You may also want to consider cooperating > with the maintainer of the conflicting tree to minimise any particularly > complex conflicts. Thanks for the notification, merge looks correct to me, Jonathan? greg k-h