From: Jani Nikula <jani.nikula@intel.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
"Luca Coelho" <luciano.coelho@intel.com>
Subject: Re: Re: [PATCH drm-misc-next] drm/xe: Fix a missing argument to drm_err_printer
Date: Tue, 13 Feb 2024 16:40:19 +0200 [thread overview]
Message-ID: <87a5o48m24.fsf@intel.com> (raw)
In-Reply-To: <yjeqfuxc3az2j5bbvt7g5wtjmulcuxhill2n2hspjsmiokxfnb@pdd27bmfvd2m>
On Tue, 13 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> On Mon, Feb 12, 2024 at 12:53:05PM +0200, Jani Nikula wrote:
>> On Mon, 12 Feb 2024, Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
>> > The indicated commit below added a device argument to the
>> > function, but there was a call in the xe driver that was
>> > not properly changed.
>>
>> Aww, crap. Looks like my drm-misc-next configs don't have xe enabled.
>
> FTR, there's defconfigs in the drm-rerere repo that are fairly well maintained.
None of them have CONFIG_DRM_XE enabled.
What's the procedure for updating the defconfigs? Do we have it
documented somewhere?
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-13 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 10:38 [PATCH drm-misc-next] drm/xe: Fix a missing argument to drm_err_printer Thomas Hellström
2024-02-12 10:50 ` Maxime Ripard
2024-02-12 10:53 ` Jani Nikula
2024-02-13 14:26 ` Maxime Ripard
2024-02-13 14:40 ` Jani Nikula [this message]
2024-02-14 9:38 ` Maxime Ripard
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=87a5o48m24.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@intel.com \
--cc=mripard@kernel.org \
--cc=thomas.hellstrom@linux.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;
as well as URLs for NNTP newsgroup(s).