Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Deucher\, Alexander" <Alexander.Deucher@amd.com>,
	"dim-tools\@lists.freedesktop.org"
	<dim-tools@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"Koenig,  Christian" <Christian.Koenig@amd.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip
Date: Mon, 24 May 2021 15:05:22 +0300	[thread overview]
Message-ID: <87eedwcp6l.fsf@intel.com> (raw)
In-Reply-To: <87h7iscpet.fsf@intel.com>

On Mon, 24 May 2021, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 19 May 2021, "Deucher, Alexander" <Alexander.Deucher@amd.com> wrote:
>> [AMD Public Use]
>>
>>> -----Original Message-----
>>> From: Jani Nikula <jani.nikula@intel.com>
>>> Sent: Wednesday, May 19, 2021 4:50 AM
>>> To: dim-tools@lists.freedesktop.org
>>> Cc: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org;
>>> jani.nikula@intel.com; Deucher, Alexander
>>> <Alexander.Deucher@amd.com>; Koenig, Christian
>>> <Christian.Koenig@amd.com>; Pan; Pan, Xinhui <Xinhui.Pan@amd.com>;
>>> Daniel Vetter <daniel.vetter@ffwll.ch>
>>> Subject: [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip
>>> 
>>> We've had a stale repo for amd in drm-tip since around v4.15 i.e. for more
>>> than three years. Nobody seems to notice or care. Drop the amd branches
>>> from drm-tip.
>>> 
>>> Having the current amd branches in drm-tip would be nice to have, if only to
>>> have a common drm integration tree. However, maintaining that has a cost
>>> due to the inevitable conflicts. We can add the branches back if and when
>>> there's interest in sharing the burden.
>>> 
>>> Cc: Alex Deucher <alexander.deucher@amd.com>
>>> Cc: Christian König <christian.koenig@amd.com>
>>> Cc: Pan, Xinhui <Xinhui.Pan@amd.com>
>>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>
>> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>
> Thanks, pushed out and rebuilt drm-tip.

Note that drm-tip is unchanged after this, apart from the
integration-manifest.


BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2021-05-24 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:49 [Intel-gfx] [drm-rerere PATCH] nightly.conf: drop amd branches from drm-tip Jani Nikula
2021-05-19 10:14 ` Daniel Vetter
2021-05-19 11:01 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2021-05-19 13:28 ` [Intel-gfx] [drm-rerere PATCH] " Deucher, Alexander
2021-05-24 12:00   ` Jani Nikula
2021-05-24 12:05     ` Jani Nikula [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=87eedwcp6l.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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