From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
"Christoph Lameter (Ampere)" <cl@gentwo.org>
Subject: Re: [PATCH] drm/i915/gt: Use standard API for seqcount read in TLB invalidation
Date: Tue, 28 Oct 2025 12:45:56 +0000 [thread overview]
Message-ID: <DDTYRY4J7XJ5.8PR5I265OCFJ@intel.com> (raw)
In-Reply-To: <20251023132802.654061-1-andi.shyti@linux.intel.com>
On Thu Oct 23, 2025 at 1:28 PM UTC, Andi Shyti wrote:
> seqprop_sequence() is not intended for use outside seqlock.h.
> Although it is accessible as a macro, it is meant to be used only
> internally within the header.
>
> Replace it with its proper wrapper, raw_read_seqcount().
>
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> Co-developed-by: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Christoph Lameter (Ampere) <cl@gentwo.org>
> ---
LGTM
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2025-10-28 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 13:28 [PATCH] drm/i915/gt: Use standard API for seqcount read in TLB invalidation Andi Shyti
2025-10-23 16:36 ` ✓ i915.CI.BAT: success for drm/i915/gt: Use standard API for seqcount read in TLB invalidation (rev2) Patchwork
2025-10-24 5:40 ` ✓ i915.CI.Full: " Patchwork
2025-10-28 12:45 ` Sebastian Brzezinka [this message]
2025-10-31 9:59 ` [PATCH] drm/i915/gt: Use standard API for seqcount read in TLB invalidation Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 9:15 Andi Shyti
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=DDTYRY4J7XJ5.8PR5I265OCFJ@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=cl@gentwo.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.