From: Danilo Krummrich <dakr@redhat.com>
To: Luben Tuikov <luben.tuikov@amd.com>,
airlied@gmail.com, daniel@ffwll.ch, matthew.brost@intel.com,
boris.brezillon@collabora.com, christian.koenig@amd.com,
faith.ekstrand@collabora.com
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH drm-misc-next 1/3] drm/sched: implement dynamic job flow control
Date: Wed, 27 Sep 2023 02:18:31 +0200 [thread overview]
Message-ID: <2b062434-fcbd-de2b-decd-5000b63c2e6f@redhat.com> (raw)
In-Reply-To: <f6294659-042d-46eb-ae6e-716a6c51872d@amd.com>
Hi,
On 9/27/23 01:48, Luben Tuikov wrote:
> Hi,
>
> Please also CC me to the whole set, as opposed to just one patch of the set.
> And so in the future.
There is no series. I created a series in the first place, but finally decided to
send this one and a few driver patches separately. However, I just accidentally
sent out the wrong one still containing the "1/3" addition.
- Danilo
>
> Thanks!
next prev parent reply other threads:[~2023-09-27 3:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 22:43 Danilo Krummrich
2023-09-25 12:55 ` Boris Brezillon
2023-09-25 17:55 ` Christian König
2023-09-26 7:11 ` Boris Brezillon
2023-09-27 11:54 ` Christian König
2023-09-27 12:11 ` Danilo Krummrich
2023-09-27 12:15 ` Christian König
2023-09-27 12:41 ` Luben Tuikov
2023-09-27 14:12 ` Danilo Krummrich
2023-09-28 8:02 ` Boris Brezillon
2023-09-28 14:44 ` Luben Tuikov
2023-09-28 16:26 ` Boris Brezillon
2023-09-26 20:43 ` Luben Tuikov
2023-09-26 23:48 ` Luben Tuikov
2023-09-27 0:18 ` Danilo Krummrich [this message]
2023-09-27 0:13 ` Danilo Krummrich
2023-09-27 1:55 ` Luben Tuikov
2023-09-27 7:25 ` Boris Brezillon
2023-09-27 11:45 ` Danilo Krummrich
2023-09-27 11:54 ` Boris Brezillon
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=2b062434-fcbd-de2b-decd-5000b63c2e6f@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=matthew.brost@intel.com \
--cc=nouveau@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
all inboxes | Powered by JetHome®