From: Jani Nikula <jani.nikula@linux.intel.com>
To: Luca Coelho <luca@coelho.fi>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Luca Coelho <luciano.coelho@intel.com>
Cc: intel-gfx@lists.freedesktop.org, gustavo.sousa@intel.com
Subject: Re: [PATCH] drm/xe/display: fix type of intel_uncore_read*() functions
Date: Wed, 20 Mar 2024 12:11:59 +0200 [thread overview]
Message-ID: <874jd1nrf4.fsf@intel.com> (raw)
In-Reply-To: <311efe399cedd3b9ee95e5aac98e1c8956092d0a.camel@coelho.fi>
On Tue, 19 Mar 2024, Luca Coelho <luca@coelho.fi> wrote:
> On Tue, 2024-03-19 at 17:06 +0200, Jani Nikula wrote:
>> On Tue, 19 Mar 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
>> > On Thu, Mar 14, 2024 at 08:52:21AM +0200, Luca Coelho wrote:
>> > > Some of the backported intel_uncore_read*() functions used the wrong
>> > > types. Change the function declarations accordingly.
>> > >
>> > > Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
>> > > Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
>> >
>> > if a patch affects xe, please always Cc the xe mailing list so it
>> > triggers CI on those machines
>>
>> Indeed. I just bounced the patch to intel-xe to trigger CI.
>
> Thanks, guys! I'll do it always from now on.
Thanks for the patch and review, pushed to drm-xe-next.
BR,
Jani.
>
> --
> Cheers,
> Luca.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-03-20 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 6:52 [PATCH] drm/xe/display: fix type of intel_uncore_read*() functions Luca Coelho
2024-03-14 8:21 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-03-14 23:16 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-19 10:46 ` Luca Coelho
2024-03-19 14:52 ` [PATCH] " Lucas De Marchi
2024-03-19 15:06 ` Jani Nikula
2024-03-19 15:14 ` Luca Coelho
2024-03-20 10:11 ` Jani Nikula [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=874jd1nrf4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luca@coelho.fi \
--cc=lucas.demarchi@intel.com \
--cc=luciano.coelho@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