From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, scott.k.mitch1@gmail.com,
Bruce Richardson <bruce.richardson@intel.com>,
Kevin Laatz <kevin.laatz@intel.com>,
Conor Walsh <conor.walsh@intel.com>
Subject: Re: [PATCH] dma/idxd: mark portal pointer as volatile
Date: Mon, 16 Feb 2026 18:28:34 +0100 [thread overview]
Message-ID: <5971878.DCG2G0Ltq2@thomas> (raw)
In-Reply-To: <20260126101357.2770431-1-bruce.richardson@intel.com>
26/01/2026 11:13, Bruce Richardson:
> The portal pointer for writing descriptors to the idxd device should be
> volatile for consistency with how it is used. Only time we need to cast
> away the volatility is when unmapping it.
>
> Bugzilla ID: 1871
> Fixes: e888bb1278c6 ("dma/idxd: add bus device probing")
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks.
prev parent reply other threads:[~2026-02-16 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1871-3@http.bugs.dpdk.org>
2026-01-26 10:13 ` [PATCH] dma/idxd: mark portal pointer as volatile Bruce Richardson
2026-02-16 17:28 ` Thomas Monjalon [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=5971878.DCG2G0Ltq2@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=scott.k.mitch1@gmail.com \
--cc=stable@dpdk.org \
/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.