The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Qianfeng Rong <rongqianfeng@vivo.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Dave Penkler <dpenkler@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michael Rubin <matchstick@neverthere.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gpib: use int instead of u32 to store error codes
Date: Tue, 26 Aug 2025 19:49:01 +0800	[thread overview]
Message-ID: <fcdb1a32-a7a1-4dc7-bbcf-58d802743b79@vivo.com> (raw)
In-Reply-To: <aK2KHhaFqWbd5S_O@stanley.mountain>


在 2025/8/26 18:19, Dan Carpenter 写道:
> On Tue, Aug 26, 2025 at 05:58:59PM +0800, Qianfeng Rong wrote:
>> Use int instead of size_t for 'ret' variable to store negative error codes
>> returned by bb_write().
>>
> The commit message needs to give a motivation.  I would have assumed from
> reading the patch that this caused a signedness bug but it doesn't.
> The commit has no effect on runtime but fixing the type is a nice
> cleanup.  My commit message would say:
>
> The "ret" variable is used to store the return from bb_write() returns
> either zero on success or negative error codes on failure.  Storing the
> error codes in size_t which is an unsigned long, doesn't cause an issue
> at runtime but it's ugly as pants.  Change "ret" from size_t to int
> type.  No effect on runtime.


Thanks very much for the detailed comments.  I will send v2 with a commit
message similar to the one you suggested.

Best regards,
Qianfeng

      reply	other threads:[~2025-08-26 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  9:58 [PATCH] staging: gpib: use int instead of u32 to store error codes Qianfeng Rong
2025-08-26 10:19 ` Dan Carpenter
2025-08-26 11:49   ` Qianfeng Rong [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=fcdb1a32-a7a1-4dc7-bbcf-58d802743b79@vivo.com \
    --to=rongqianfeng@vivo.com \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=dpenkler@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=matchstick@neverthere.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox