From: Swati Sharma <swati2.sharma@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] Revert VDSC lib changes
Date: Fri, 20 Jan 2023 21:39:57 +0530 [thread overview]
Message-ID: <77a5b9bb-6951-0cf7-fd19-09c0cff19601@intel.com> (raw)
In-Reply-To: <Y8qz8KK5DsFHW3Oe@platvala-desk.ger.corp.intel.com>
On 20-Jan-23 9:02 PM, Petri Latvala wrote:
> On Fri, Jan 20, 2023 at 04:47:58PM +0200, Petri Latvala wrote:
>> On Fri, Jan 20, 2023 at 08:15:00PM +0530, Swati Sharma wrote:
>>> This reverts
>>> commit 2a611c37bd170763052bf6c17aa2d48cf09a63c1
>>> commit 65202cbc6109f17cf786a95947f4ee9223aec6b8
>>> commit b6984b946ba66f6bb0452b223fe188429ddeab34
>>> commit bbc2a5ceadb656552c5bcf95a19ce2b292a78128
>>>
>>> Series broke git pipeline, revert above commits.
>>>
>>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>>
>> The ultimate root cause is gitlab CI using Debian buster and thus
>> libdrm 2.4.97. Until that's changed (soon) #include <stddef.h> and
>> maybe some others need to be liberally applied all around.
>>
>> Thanks for the quick revert.
>>
>> Acked-by: Petri Latvala <petri.latvala@intel.com>
>
> Gitlab pipeline for this series was a success, go ahead and merge.
Done.
>
>
--
~Swati Sharma
next prev parent reply other threads:[~2023-01-20 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 14:45 [igt-dev] [PATCH i-g-t] Revert VDSC lib changes Swati Sharma
2023-01-20 14:47 ` Petri Latvala
2023-01-20 15:15 ` Kamil Konieczny
2023-01-20 15:22 ` Kamil Konieczny
2023-01-20 15:32 ` Petri Latvala
2023-01-20 16:09 ` Swati Sharma [this message]
2023-01-20 15:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-21 18:57 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=77a5b9bb-6951-0cf7-fd19-09c0cff19601@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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