From: "Christian König" <christian.koenig@amd.com>
To: "Yang, Fei" <fei.yang@intel.com>, Simon Ser <contact@emersion.fr>,
"Kempczynski, Zbigniew" <zbigniew.kempczynski@intel.com>,
"Konieczny, Kamil" <kamil.konieczny@intel.com>,
"Chehab, Mauro" <mauro.chehab@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH v2] drm-uapi: sync with drm-next
Date: Thu, 19 Oct 2023 11:11:22 +0200 [thread overview]
Message-ID: <91abb24d-ed21-442c-bc81-fcc57a429969@amd.com> (raw)
In-Reply-To: <BYAPR11MB2567390FE41325FF67C36EE69AD5A@BYAPR11MB2567.namprd11.prod.outlook.com>
Am 18.10.23 um 23:23 schrieb Yang, Fei:
>> Any news about this? Can I get a R-b?
> I'm not the right person to review this. Maybe Kamil and Mauro can help here?
I'm also not feeling like I'm deep enough into the procedure to judge if
that's correct or not.
But as far as I know libdrm changes are now reviewed as merge requests
and not on the mailing list any more.
Regards,
Christian.
next prev parent reply other threads:[~2023-10-19 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 17:43 [igt-dev] [PATCH v2] drm-uapi: sync with drm-next Simon Ser
2023-07-27 18:27 ` [igt-dev] ✗ GitLab.Pipeline: warning for drm-uapi: sync with drm-next (rev2) Patchwork
2023-07-27 18:51 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-07-27 19:58 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-27 23:14 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-28 8:21 ` [igt-dev] [PATCH v2] drm-uapi: sync with drm-next Zbigniew Kempczyński
2023-07-28 8:31 ` Simon Ser
2023-07-28 8:49 ` Zbigniew Kempczyński
2023-07-28 8:57 ` Simon Ser
2023-07-28 9:09 ` Zbigniew Kempczyński
2023-10-18 12:43 ` Simon Ser
2023-10-18 21:23 ` Yang, Fei
2023-10-19 9:11 ` Christian König [this message]
2023-10-19 12:02 ` Simon Ser
2023-10-19 8:41 ` Zbigniew Kempczyński
2023-10-19 10:25 ` Kamil Konieczny
2023-10-19 14:24 ` Simon Ser
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=91abb24d-ed21-442c-bc81-fcc57a429969@amd.com \
--to=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=fei.yang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=mauro.chehab@intel.com \
--cc=tvrtko.ursulin@intel.com \
--cc=zbigniew.kempczynski@intel.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