All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>
Cc: DRI <dri-devel@lists.freedesktop.org>,
	Julian Braha <julianbraha@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Robert Foss <robert.foss@linaro.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
Date: Fri, 18 Mar 2022 12:06:47 +1100	[thread overview]
Message-ID: <20220318120647.2c89bf05@canb.auug.org.au> (raw)
In-Reply-To: <20220318115544.0c977415@canb.auug.org.au>

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

Hi all,

On Fri, 18 Mar 2022 11:55:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm tree got a conflict in:
> 
>   drivers/gpu/drm/bridge/Kconfig
> 
> between commit:
> 
>   3c3384050d68 ("drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS")
> 
> from the drm-misc-fixes tree and commit:
> 
>   803abfd8dda5 ("drm: bridge: fix unmet dependency on DRM_KMS_HELPER for DRM_PANEL_BRIDGE")
> 
> from the drm tree.
> 
> I fixed it up (I just used the latter) and can carry the fix as

But that failed during configuration, so I went back and used the
former change.

> 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

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Robert Foss <robert.foss@linaro.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Julian Braha <julianbraha@gmail.com>
Subject: Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
Date: Fri, 18 Mar 2022 12:06:47 +1100	[thread overview]
Message-ID: <20220318120647.2c89bf05@canb.auug.org.au> (raw)
In-Reply-To: <20220318115544.0c977415@canb.auug.org.au>

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

Hi all,

On Fri, 18 Mar 2022 11:55:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm tree got a conflict in:
> 
>   drivers/gpu/drm/bridge/Kconfig
> 
> between commit:
> 
>   3c3384050d68 ("drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS")
> 
> from the drm-misc-fixes tree and commit:
> 
>   803abfd8dda5 ("drm: bridge: fix unmet dependency on DRM_KMS_HELPER for DRM_PANEL_BRIDGE")
> 
> from the drm tree.
> 
> I fixed it up (I just used the latter) and can carry the fix as

But that failed during configuration, so I went back and used the
former change.

> 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

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

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Robert Foss <robert.foss@linaro.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Julian Braha <julianbraha@gmail.com>
Subject: Re: [Intel-gfx] linux-next: manual merge of the drm tree with the drm-misc-fixes tree
Date: Fri, 18 Mar 2022 12:06:47 +1100	[thread overview]
Message-ID: <20220318120647.2c89bf05@canb.auug.org.au> (raw)
In-Reply-To: <20220318115544.0c977415@canb.auug.org.au>

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

Hi all,

On Fri, 18 Mar 2022 11:55:44 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the drm tree got a conflict in:
> 
>   drivers/gpu/drm/bridge/Kconfig
> 
> between commit:
> 
>   3c3384050d68 ("drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS")
> 
> from the drm-misc-fixes tree and commit:
> 
>   803abfd8dda5 ("drm: bridge: fix unmet dependency on DRM_KMS_HELPER for DRM_PANEL_BRIDGE")
> 
> from the drm tree.
> 
> I fixed it up (I just used the latter) and can carry the fix as

But that failed during configuration, so I went back and used the
former change.

> 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

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

  reply	other threads:[~2022-03-18  1:06 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  0:55 linux-next: manual merge of the drm tree with the drm-misc-fixes tree Stephen Rothwell
2022-03-18  0:55 ` [Intel-gfx] " Stephen Rothwell
2022-03-18  0:55 ` Stephen Rothwell
2022-03-18  1:06 ` Stephen Rothwell [this message]
2022-03-18  1:06   ` [Intel-gfx] " Stephen Rothwell
2022-03-18  1:06   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22  0:29 Stephen Rothwell
2023-11-22  0:29 ` Stephen Rothwell
2023-11-28 10:04 ` Geert Uytterhoeven
2023-11-28 10:04   ` Geert Uytterhoeven
2023-09-28  2:05 Stephen Rothwell
2023-09-28  2:05 ` Stephen Rothwell
2023-06-27  1:54 Stephen Rothwell
2023-06-27  1:54 ` Stephen Rothwell
2023-07-11  1:17 ` Stephen Rothwell
2023-07-11  1:17   ` Stephen Rothwell
2022-11-21  2:06 Stephen Rothwell
2022-11-21  2:06 ` Stephen Rothwell
2022-07-11  2:47 Stephen Rothwell
2022-07-11  2:47 ` Stephen Rothwell
2022-07-11  8:05 ` Christian König
2022-07-11  8:05   ` Christian König
2022-07-17 23:44   ` Stephen Rothwell
2022-07-17 23:44     ` Stephen Rothwell
2022-07-19  7:35     ` Geert Uytterhoeven
2022-07-19  7:35       ` Geert Uytterhoeven
2022-07-27  2:55     ` Stephen Rothwell
2022-07-27  2:55       ` Stephen Rothwell
2022-07-27  3:24       ` Dave Airlie
2022-07-27  3:24         ` Dave Airlie
2022-07-27  5:37         ` Stephen Rothwell
2022-07-27  5:37           ` Stephen Rothwell
2021-12-22  3:50 Stephen Rothwell
2021-12-22  3:50 ` Stephen Rothwell
2021-12-22  7:31 ` Christian König
2021-12-22  7:31   ` Christian König
2021-11-29 23:33 Stephen Rothwell
2021-11-29 23:33 ` Stephen Rothwell
2021-11-30  8:58 ` Maxime Ripard
2021-11-30  8:58   ` Maxime Ripard
2021-11-30 20:35   ` Stephen Rothwell
2021-11-30 20:35     ` Stephen Rothwell
2021-10-22  0:53 Stephen Rothwell
2021-06-17  1:42 Stephen Rothwell
2021-06-17  1:42 ` Stephen Rothwell
2021-04-09  3:12 Stephen Rothwell
2021-04-09  3:12 ` Stephen Rothwell
2021-03-18  1:02 Stephen Rothwell
2021-03-18  1:02 ` Stephen Rothwell
2021-03-18  6:51 ` Tomi Valkeinen
2021-03-18  6:51   ` Tomi Valkeinen
2020-07-28  3:41 Stephen Rothwell
2020-07-28  3:41 ` Stephen Rothwell
2020-05-01  3:45 Stephen Rothwell
2020-05-01  3:45 ` Stephen Rothwell
2020-03-01 23:43 Stephen Rothwell
2020-03-01 23:43 ` Stephen Rothwell
2019-09-15 21:18 Mark Brown
2019-09-16  5:29 ` Vasily Khoruzhick
2019-09-17  2:43   ` Qiang Yu
2019-08-26  3:06 Stephen Rothwell
2019-08-29 10:11 ` james qian wang (Arm Technology China)
2019-08-29 10:11   ` james qian wang (Arm Technology China)
2018-11-26  2:37 Stephen Rothwell
2018-03-08  0:47 Stephen Rothwell
2017-12-13 23:59 Stephen Rothwell
2017-12-13 23:59 ` Stephen Rothwell
2017-01-17  0:59 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=20220318120647.2c89bf05@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=julianbraha@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robert.foss@linaro.org \
    --cc=tzimmermann@suse.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 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.