From: "Christian König" <christian.koenig@amd.com>
To: Boris Brezillon <boris.brezillon@collabora.com>,
Nathan Chancellor <nathan@kernel.org>
Cc: ndesaulniers@google.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
daniel@ffwll.ch, trix@redhat.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, naresh.kamboju@linaro.org, dakr@redhat.com
Subject: Re: [PATCH 1/2] drm/exec: use unique instead of local label
Date: Thu, 10 Aug 2023 08:48:05 +0200 [thread overview]
Message-ID: <7a09909a-4c94-2e4b-dd9a-4bd019b67585@amd.com> (raw)
In-Reply-To: <20230810084002.636cc827@collabora.com>
Am 10.08.23 um 08:40 schrieb Boris Brezillon:
> On Wed, 9 Aug 2023 08:37:55 -0700
> Nathan Chancellor <nathan@kernel.org> wrote:
>
>> Hi Christian,
>>
>> Can this be applied to drm-misc? Other drivers are starting to make use
>> of this API and our builds with clang-17 and clang-18 have been broken
>> for some time due to this.
> Queued to drm-misc-next.
Sorry for the delay I have been on vacation last week and haven't yet
catched up to this point in my mails.
Thanks for taking care of this,
Christian.
next prev parent reply other threads:[~2023-08-10 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:36 Christian König
2023-07-31 12:36 ` [PATCH 2/2] drm/exec: add test case for using a drm_exec multiple times Christian König
2023-07-31 15:31 ` [PATCH 1/2] drm/exec: use unique instead of local label Nathan Chancellor
2023-07-31 16:00 ` Boris Brezillon
2023-08-01 20:35 ` Nick Desaulniers
2023-08-02 8:44 ` Boris Brezillon
2023-08-02 21:24 ` Nick Desaulniers
2023-08-10 8:29 ` Rasmus Villemoes
2023-08-09 15:37 ` Nathan Chancellor
2023-08-10 6:40 ` Boris Brezillon
2023-08-10 6:48 ` Christian König [this message]
2023-08-10 14:38 ` Nathan Chancellor
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=7a09909a-4c94-2e4b-dd9a-4bd019b67585@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.com \
--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 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®