From: Jani Nikula <jani.nikula@intel.com>
To: "Hogander, Jouni" <jouni.hogander@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 0/2] Backport including i915_active.h in intel_frontbuffer.c
Date: Wed, 11 Oct 2023 15:51:50 +0300 [thread overview]
Message-ID: <878r894909.fsf@intel.com> (raw)
In-Reply-To: <69012691aecbdb459d37451827900f7b415ba3d8.camel@intel.com>
On Mon, 02 Oct 2023, "Hogander, Jouni" <jouni.hogander@intel.com> wrote:
> On Mon, 2023-10-02 at 10:04 +0300, Jani Nikula wrote:
>> On Mon, 02 Oct 2023, Jouni Högander <jouni.hogander@intel.com> wrote:
>> > Including i915_active.h in intel_frontbuffer.h is now merged into
>> > upstream. Let's revert similar patch from drm-xe-next and backport
>> > from upstream.
>>
>> Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> Thank you Jani. These are now merged.
I don't know what happened, but they were nowhere to be found. Maybe
lost in a rebase, with the wrong one left in the tree?
Anyway, pushed again.
BR,
Jani.
>
> BR,
>
> Jouni Högander
>
>>
>> >
>> > Cc: Jani Nikula <jani.nikula@intel.com>
>> >
>> > Jouni Högander (2):
>> > Revert "drm/i915/display: Include i915_active header"
>> > drm/i915/display: Include i915_active header in frontbuffer
>> > tracking
>> > code
>>
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-11 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 6:58 [Intel-xe] [PATCH 0/2] Backport including i915_active.h in intel_frontbuffer.c Jouni Högander
2023-10-02 6:58 ` [Intel-xe] [PATCH 1/2] Revert "drm/i915/display: Include i915_active header" Jouni Högander
2023-10-02 6:58 ` [Intel-xe] [PATCH 2/2] drm/i915/display: Include i915_active header in frontbuffer tracking code Jouni Högander
2023-10-02 7:04 ` [Intel-xe] [PATCH 0/2] Backport including i915_active.h in intel_frontbuffer.c Jani Nikula
2023-10-02 10:33 ` Hogander, Jouni
2023-10-11 12:51 ` Jani Nikula [this message]
2023-10-12 7:06 ` Hogander, Jouni
2023-10-02 8:00 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-10-02 8:00 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-02 8:02 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-02 8:09 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-02 8:09 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-02 8:11 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-02 8:48 ` [Intel-xe] ✓ CI.BAT: success " 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=878r894909.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=rodrigo.vivi@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