[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210827164904.6b1d1f0e@canb.auug.org.au>
Date: Fri, 27 Aug 2021 16:49:04 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jakub Kicinski <kuba@...nel.org>,
Kalle Valo <kvalo@...eaurora.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Loic Poulain <loic.poulain@...aro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Subject: linux-next: manual merge of the char-misc tree with Linus' tree
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.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists