[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190709101754.1836ac73@canb.auug.org.au>
Date: Tue, 9 Jul 2019 10:17:54 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Guenter Roeck <linux@...ck-us.net>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Fabian Schindlatz <fabian.schindlatz@....de>,
Len Brown <len.brown@...el.com>
Subject: Re: linux-next: manual merge of the tip tree with the hwmon-staging
tree
Hi all,
On Mon, 1 Jul 2019 17:15:24 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> drivers/hwmon/coretemp.c
>
> between commit:
>
> 601fdf7e6635 ("hwmon: Correct struct allocation style")
>
> from the hwmon-staging tree and commit:
>
> 835896a59b95 ("hwmon/coretemp: Cosmetic: Rename internal variables to zones from packages")
>
> from the tip tree.
>
> I fixed it up (the comment fixed in the latter was also fixed in the
> former) 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.
I am still getting this conflict (the commit ids may have changed).
Just a reminder in case you think Linus may need to know.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists