From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Jakub Kicinski <kuba@kernel.org>,
Kalle Valo <kvalo@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Loic Poulain <loic.poulain@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: linux-next: manual merge of the char-misc tree with Linus' tree
Date: Fri, 27 Aug 2021 15:12:02 +0200 [thread overview]
Message-ID: <YSjkosA6yMrMmaNk@kroah.com> (raw)
In-Reply-To: <20210827164904.6b1d1f0e@canb.auug.org.au>
On Fri, Aug 27, 2021 at 04:49:04PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got conflicts in:
>
> drivers/bus/mhi/core/main.c
> net/qrtr/mhi.c
>
> between commit:
>
> 9ebc2758d0bb ("Revert "net: really fix the build..."")
>
> from the origin tree and commit:
>
> 0092a1e3f763 ("bus: mhi: Add inbound buffers allocation flag")
>
> from the char-misc tree.
>
> I fixed it up (the commit in Linus' tree is basically a revert of the
> char-misc tree, so I effectively reverted the latter) 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.
Hm, what should I do in my tree here?
Kalle, what commit should I make in the char-misc tree now to handle
this issue, and make the merge with Linus's tree "simple"? Or any other
ideas?
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-27 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 6:49 linux-next: manual merge of the char-misc tree with Linus' tree Stephen Rothwell
2021-08-27 13:12 ` Greg KH [this message]
2021-08-27 16:24 ` Kalle Valo
2021-08-27 17:55 ` Manivannan Sadhasivam
2021-08-27 17:58 ` Manivannan Sadhasivam
2021-08-27 19:28 ` Greg KH
2021-08-28 7:27 ` Kalle Valo
2021-08-28 7:50 ` Greg KH
2021-08-28 9:51 ` Manivannan Sadhasivam
-- strict thread matches above, loose matches on Subject: below --
2020-07-27 7:56 Stephen Rothwell
2020-07-27 7:46 Stephen Rothwell
2013-07-29 5:01 Stephen Rothwell
2013-07-29 19:26 ` Greg KH
2013-07-29 22:16 ` Tomas Winkler
2013-07-29 22:25 ` Greg KH
2013-07-30 0:27 ` Stephen Rothwell
2013-07-30 1:38 ` Greg KH
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=YSjkosA6yMrMmaNk@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.