From: Dave Jiang <dave.jiang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>
Cc: <vishal.l.verma@intel.com>, <jonathan.cameron@huawei.com>,
<fan.ni@samsung.com>, <a.manzanares@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/3] cxl/memdev: Document security state in kern-doc
Date: Fri, 28 Jul 2023 11:02:18 -0700 [thread overview]
Message-ID: <b6b58948-494f-7d04-3572-4e63174b3a2b@intel.com> (raw)
In-Reply-To: <20230726051940.3570-3-dave@stgolabs.net>
On 7/25/23 22:19, Davidlohr Bueso wrote:
> ... as is the case with all members of struct cxl_memdev_state.
>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/cxlmem.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index 79e99c873ca2..083c6e58bc49 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -434,6 +434,7 @@ struct cxl_dev_state {
> * @next_persistent_bytes: persistent capacity change pending device reset
> * @event: event log driver state
> * @poison: poison driver state info
> + * @security: security driver state info
> * @fw: firmware upload / activation state
> * @mbox_send: @dev specific transport for transmitting mailbox commands
> *
next prev parent reply other threads:[~2023-07-28 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 5:19 [PATCH 0/3] cxl/memdev: Make sanitize interfaces conditionally available Davidlohr Bueso
2023-07-26 5:19 ` [PATCH 1/3] cxl/memdev: Improve sanitize ABI descriptions Davidlohr Bueso
2023-07-28 18:01 ` Dave Jiang
2023-08-04 14:02 ` Jonathan Cameron
2023-08-11 14:58 ` Davidlohr Bueso
2023-07-26 5:19 ` [PATCH 2/3] cxl/memdev: Document security state in kern-doc Davidlohr Bueso
2023-07-28 18:02 ` Dave Jiang [this message]
2023-07-26 5:19 ` [PATCH 3/3] cxl/memdev: Only show sanitize sysfs files when supported Davidlohr Bueso
2023-07-28 18:12 ` Dave Jiang
2023-08-04 14:16 ` Jonathan Cameron
2023-08-04 23:50 ` Davidlohr Bueso
-- strict thread matches above, loose matches on Subject: below --
2024-04-22 7:01 [PATCH 1/3] cxl/memdev: Improve sanitize ABI descriptions Dongsheng Yang
2024-04-22 7:01 ` [PATCH 2/3] cxl/memdev: Document security state in kern-doc Dongsheng Yang
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=b6b58948-494f-7d04-3572-4e63174b3a2b@intel.com \
--to=dave.jiang@intel.com \
--cc=a.manzanares@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@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