mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Guenter Roeck <linux@roeck-us.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Fabian Schindlatz <fabian.schindlatz@fau.de>,
	Len Brown <len.brown@intel.com>
Subject: Re: linux-next: manual merge of the tip tree with the hwmon-staging tree
Date: Tue, 9 Jul 2019 10:17:54 +1000	[thread overview]
Message-ID: <20190709101754.1836ac73@canb.auug.org.au> (raw)
In-Reply-To: <20190701171524.774dfc75@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

Hi all,

On Mon, 1 Jul 2019 17:15:24 +1000 Stephen Rothwell <sfr@canb.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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-07-09  0:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01  7:15 Stephen Rothwell
2019-07-09  0:17 ` Stephen Rothwell [this message]
2019-07-09  1:21   ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2026-06-08 14:31 Mark Brown
2026-06-09  7:06 ` Ingo Molnar
2018-12-11  3:30 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190709101754.1836ac73@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=fabian.schindlatz@fau.de \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®