From: Jani Nikula <jani.nikula@intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Danilo Krummrich" <dakr@redhat.com>,
"David Airlie" <airlied@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Hamza Mahfooz" <hamza.mahfooz@amd.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Karol Herbst" <kherbst@redhat.com>,
"Lyude Paul" <lyude@redhat.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Maxime Ripard" <mripard@kernel.org>,
Xinhui.Pan@amd.com, "Rob Clark" <robdclark@gmail.com>,
"Sean Paul" <sean@poorly.run>,
"Sui Jingfeng" <sui.jingfeng@linux.dev>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [RESEND v3 0/2] drm: enable W=1 warnings by default across the subsystem
Date: Tue, 05 Mar 2024 19:43:07 +0200 [thread overview]
Message-ID: <8734t41sno.fsf@intel.com> (raw)
In-Reply-To: <0df557af4aaceeb1ef85ee3c74169ee9@kernel.org>
On Tue, 05 Mar 2024, "Maxime Ripard" <mripard@kernel.org> wrote:
> On Tue, 5 Mar 2024 11:07:34 +0200, Jani Nikula wrote:
>> Resend of [1] with an intent to merge after the CI results come in. This
>> is aiming for v6.10, so we'll have maximal time to find all the issues
>> my configs didn't catch.
>>
>> I built this on x86-64 (both gcc and clang), arm and arm64, and
>>
>> [ ... ]
>
> Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks everyone for acks and reviews, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-05 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 9:07 [RESEND v3 0/2] drm: enable W=1 warnings by default across the subsystem Jani Nikula
2024-03-05 9:07 ` [RESEND v3 1/2] drm: enable (most) " Jani Nikula
2024-05-17 21:04 ` Guenter Roeck
2024-03-05 9:07 ` [RESEND v3 2/2] drm: Add CONFIG_DRM_WERROR Jani Nikula
2024-03-05 10:14 ` Javier Martinez Canillas
2024-03-26 22:56 ` Nathan Chancellor
2024-03-27 7:34 ` Maxime Ripard
2024-03-27 7:59 ` Jani Nikula
2024-03-27 16:33 ` Nathan Chancellor
2024-03-28 11:33 ` Jani Nikula
2024-03-05 11:29 ` [RESEND v3 0/2] drm: enable W=1 warnings by default across the subsystem Maxime Ripard
2024-03-05 17:43 ` Jani Nikula [this message]
2024-03-05 17:45 ` Lucas De Marchi
2024-03-05 17:50 ` Jani Nikula
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=8734t41sno.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=sui.jingfeng@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).