From: Li Ming <ming.li@zohomail.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
dave@stgolabs.net, jonathan.cameron@huawei.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH v2 1/1] cxl/feature: Update out_len in set feature failure case
Date: Thu, 10 Apr 2025 09:02:04 +0800 [thread overview]
Message-ID: <6bfb9815-0270-41e5-95c3-7ecefe8d46f4@zohomail.com> (raw)
In-Reply-To: <1be19059-e879-4404-a68a-10093fef7522@intel.com>
On 4/9/2025 11:37 PM, Dave Jiang wrote:
>
> On 4/8/25 7:25 PM, Li Ming wrote:
>> CXL subsystem supports userspace to configure features via fwctl
>> interface, it will configure features by using Set Feature command.
>> Whatever Set Feature succeeds or fails, CXL driver always needs to
>> return a structure fwctl_rpc_cxl_out to caller, and returned size is
>> updated in a out_len parameter. The out_len should be updated not only
>> when the set feature succeeds, but also when the set feature fails.
> Good catch! Can you add a Fixes tag please? Otherwise
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>、
Yes, forgot to add a Fixes tag. Thanks for that.
Ming
>
>> Signed-off-by: Li Ming <ming.li@zohomail.com>
>> ---
>> base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8 v6.15-rc1
>>
>> v2:
>> - Adjust changelog
>> ---
>> drivers/cxl/core/features.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
>> index f4daefe3180e..066dfc29a3dd 100644
>> --- a/drivers/cxl/core/features.c
>> +++ b/drivers/cxl/core/features.c
>> @@ -528,13 +528,13 @@ static void *cxlctl_set_feature(struct cxl_features_state *cxlfs,
>> rc = cxl_set_feature(cxl_mbox, &feat_in->uuid,
>> feat_in->version, feat_in->feat_data,
>> data_size, flags, offset, &return_code);
>> + *out_len = sizeof(*rpc_out);
>> if (rc) {
>> rpc_out->retval = return_code;
>> return no_free_ptr(rpc_out);
>> }
>>
>> rpc_out->retval = CXL_MBOX_CMD_RC_SUCCESS;
>> - *out_len = sizeof(*rpc_out);
>>
>> return no_free_ptr(rpc_out);
>> }
next prev parent reply other threads:[~2025-04-10 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 2:25 Li Ming
2025-04-09 15:37 ` Dave Jiang
2025-04-10 1:02 ` Li Ming [this message]
2025-04-09 17:58 ` Ira Weiny
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=6bfb9815-0270-41e5-95c3-7ecefe8d46f4@zohomail.com \
--to=ming.li@zohomail.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®