From: Pavel Machek <pavel@ucw.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Marek Behún" <marek.behun@nic.cz>
Subject: Re: linux-next: manual merge of the leds tree with Linus' tree
Date: Thu, 9 Apr 2020 09:58:20 +0200 [thread overview]
Message-ID: <20200409075820.GA2414@amd.ucw.cz> (raw)
In-Reply-To: <20200409131252.2dfde0b7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Hi!
> Today's linux-next merge of the leds tree got a conflict in:
>
> drivers/leds/Makefile
>
> between commit:
>
> 457386350e6a ("leds: sort Makefile entries")
>
> from Linus' tree and commit:
>
> 3953d1908b2c ("From: Marek Behún <marek.behun@nic.cz>")
> 53cb3df9dd2d ("Sort Makefile entries to reduce risk of rejects.")
>
> from the leds tree.
>
> I fixed it up (I used the latter version) 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.
>
> BTW, commit 3953d1908b2c clearly did not get applied correctly :-(
Um, sorry about that. My tree got merged to Linus, so for-next is now
for-next-next and I need to empty it.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2020-04-09 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 3:12 linux-next: manual merge of the leds tree with Linus' tree Stephen Rothwell
2020-04-09 7:58 ` Pavel Machek [this message]
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=20200409075820.GA2414@amd.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=sfr@canb.auug.org.au \
/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