mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Rob Clark <robdclark@gmail.com>, Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	daniels@collabora.com, robdclark@google.com,
	gustavo.padovan@collabora.com, guilherme.gallo@collabora.com,
	sergi.blanch.torne@collabora.com, linux-kernel@vger.kernel.org,
	robclark@freedesktop.org, david.heidelberg@collabora.com,
	Helen Mae Koike Fornazier <helen.koike@collabora.com>,
	anholt@google.com, dri-devel@lists.freedesktop.org,
	emma@anholt.net, airlied@redhat.com
Subject: Re: [PULL for v6.6] drm-misc-next
Date: Thu, 17 Aug 2023 15:38:17 +0200	[thread overview]
Message-ID: <dcff3281-9d38-a244-4844-1633039a9076@suse.de> (raw)
In-Reply-To: <CAF6AEGu8mRB_wiFeWx17Z12Eu+NnP6VLFBr5sypcnxjQyj7_sQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2241 bytes --]

Hi

Am 15.08.23 um 21:59 schrieb Rob Clark:
> On Tue, Aug 15, 2023 at 12:23 PM Dave Airlie <airlied@gmail.com> wrote:
>>
>>>> Otherwise, there should be something like a drm-ci tree, from which you
>>>> can fetch the changes directly.
>>>
>>> I asked for a pull request so that I could also merge it to msm-next
>>> so that I can do CI this cycle.  (Unlike the earlier out-of-tree
>>> version of the drm/ci yml, this version needs to be in the branch that
>>> CI runs on, so I can't use the workaround that I had in previous
>>> cycles.)
>>>
>>> Perhaps it should be a pull request targeting drm-next instead of drm-misc-next.
>>>
>>> We were going to do this one-off for this cycle and then evaluate
>>> going forward whether a drm-ci-next tree is needed.  But perhaps it is
>>> a good idea.
>>
>>
>> I'm still not 100% sure how this is going down, and I'm meant to be off today,
>>
>> Don't send this as patches to drm-misc-next, but I think we'd want
>> this in drm-next for a cycle before sending it to Linus, but maybe
>> it's not directly interfering with the kernel so it's fine
>>
>> Ideally when the real merge window opens and drm-next is merged I'd
>> want to have a branch + PR written for this against drm-next that I
>> can send to Linus separately and see how it goes.
> 
> The tricky thing is we need this patch in-tree to run CI in the first
> place.. so soak time in drm-next on it's own isn't hugely useful.  (Or
> at least I'd need to move msm-next forward to drm-next for it to be
> useful.)
> 
> I guess that is a bit of an advantage to the earlier approach that
> kept everything but the expectation files in a different git tree..

I saw that this patchset has been reviewed on dri-devel. If you don't 
want it to go through DRM misc, I guess it should really be pulled into 
drm-next directly.

Do you plan to set up auto-CI for DRM misc branches? (Sorry if this 
question has been answered before.)

Best regards
Thomas

> 
> BR,
> -R

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

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

  reply	other threads:[~2023-08-17 13:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 23:56 Helen Koike
2023-08-15  9:12 ` Jani Nikula
2023-08-15 11:53   ` Helen Mae Koike Fornazier
2023-08-15 12:31     ` Thomas Zimmermann
2023-08-15 12:35       ` Daniel Vetter
2023-08-15 12:50         ` Thomas Zimmermann
2023-08-15 14:32           ` Rob Clark
2023-08-15 19:23             ` Dave Airlie
2023-08-15 19:59               ` Rob Clark
2023-08-17 13:38                 ` Thomas Zimmermann [this message]
2023-08-15 12:32     ` Jani Nikula
2023-08-15 12:33       ` Jani Nikula

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=dcff3281-9d38-a244-4844-1633039a9076@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=anholt@google.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=david.heidelberg@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=guilherme.gallo@collabora.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robclark@freedesktop.org \
    --cc=robdclark@gmail.com \
    --cc=robdclark@google.com \
    --cc=sergi.blanch.torne@collabora.com \
    /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

all inboxes | Powered by JetHome®