From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Dave Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Laurentiu Palcu <laurentiu.palcu@nxp.com>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [Intel-gfx] linux-next: manual merge of the extcon tree with the drm-misc tree
Date: Tue, 6 Oct 2020 12:58:24 +0200 [thread overview]
Message-ID: <20201006105824.GA26735@kroah.com> (raw)
In-Reply-To: <20201006200003.1be00223@canb.auug.org.au>
On Tue, Oct 06, 2020 at 08:00:03PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 10 Sep 2020 14:18:54 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the extcon tree got a conflict in:
> >
> > MAINTAINERS
> >
> > between commit:
> >
> > f61249dddecc ("MAINTAINERS: Add entry for i.MX 8MQ DCSS driver")
> >
> > from the drm-misc tree and commit:
> >
> > d0e3c25150dd ("MAINTAINERS: Add entry for NXP PTN5150A CC driver")
> >
> > from the extcon tree.
> >
> > I fixed it up (see below) 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
> >
> > diff --cc MAINTAINERS
> > index 623c53ab5bd5,da94c9b12f1b..000000000000
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@@ -12496,14 -12430,13 +12496,21 @@@ F: drivers/iio/gyro/fxas21002c_core.
> > F: drivers/iio/gyro/fxas21002c_i2c.c
> > F: drivers/iio/gyro/fxas21002c_spi.c
> >
> > +NXP i.MX 8MQ DCSS DRIVER
> > +M: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> > +R: Lucas Stach <l.stach@pengutronix.de>
> > +L: dri-devel@lists.freedesktop.org
> > +S: Maintained
> > +F: Documentation/devicetree/bindings/display/imx/nxp,imx8mq-dcss.yaml
> > +F: drivers/gpu/drm/imx/dcss/
> > +
> > + NXP PTN5150A CC LOGIC AND EXTCON DRIVER
> > + M: Krzysztof Kozlowski <krzk@kernel.org>
> > + L: linux-kernel@vger.kernel.org
> > + S: Maintained
> > + F: Documentation/devicetree/bindings/extcon/extcon-ptn5150.yaml
> > + F: drivers/extcon/extcon-ptn5150.c
> > +
> > NXP SGTL5000 DRIVER
> > M: Fabio Estevam <festevam@gmail.com>
> > L: alsa-devel@alsa-project.org (moderated for non-subscribers)
>
> This is now a conflict between the char-misc tree and the drm tree.
Looks fine, this should be easy for Linus to resolve :)
thanks,
greg k-h
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-10-06 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 4:18 [Intel-gfx] linux-next: manual merge of the extcon tree with the drm-misc tree Stephen Rothwell
2020-10-06 9:00 ` Stephen Rothwell
2020-10-06 10:58 ` Greg KH [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=20201006105824.GA26735@kroah.com \
--to=greg@kroah.com \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=cw00.choi@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzk@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox