From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: Chia-I Wu <olvaffe@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Rob Clark <robdclark@chromium.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/2] drm/sched: use DECLARE_EVENT_CLASS
Date: Tue, 26 Apr 2022 15:13:30 -0400 [thread overview]
Message-ID: <6ad4c0d8-7a49-601a-df25-edfdf8813460@amd.com> (raw)
In-Reply-To: <CAPaKu7Tq57HEuGSAQ3EjceyAU+MxOaAFE5egKEf_xWTzpDC_rA@mail.gmail.com>
Done
Andrey
On 2022-04-26 14:52, Chia-I Wu wrote:
> That would be great. I don't have push permission.
>
> On Tue, Apr 26, 2022 at 11:25 AM Andrey Grodzovsky
> <andrey.grodzovsky@amd.com> wrote:
>> It's ok to land but it wasn't, do you have push permissions to
>> drm-misc-next ? If not, I will do it for you.
>>
>> Andrey
>>
>> On 2022-04-26 12:29, Chia-I Wu wrote:
>>> On Tue, Apr 12, 2022 at 1:48 PM Chia-I Wu <olvaffe@gmail.com> wrote:
>>>> drm_sched_job and drm_run_job have the same prototype.
>>>>
>>>> v2: rename the class from drm_sched_job_entity to drm_sched_job (Andrey)
>>>>
>>>> Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
>>>> Cc: Rob Clark <robdclark@chromium.org>
>>>> Reviewed-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
>>> This series has been reviewed. Is it ok to land (if it hasn't)?
prev parent reply other threads:[~2022-04-26 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:48 [PATCH v2 1/2] drm/sched: use DECLARE_EVENT_CLASS Chia-I Wu
2022-04-12 20:48 ` [PATCH v2 2/2] drm/sched: use __string in tracepoints Chia-I Wu
2022-04-26 16:29 ` [PATCH v2 1/2] drm/sched: use DECLARE_EVENT_CLASS Chia-I Wu
2022-04-26 18:25 ` Andrey Grodzovsky
2022-04-26 18:52 ` Chia-I Wu
2022-04-26 19:13 ` Andrey Grodzovsky [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=6ad4c0d8-7a49-601a-df25-edfdf8813460@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=olvaffe@gmail.com \
--cc=robdclark@chromium.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