public inbox for linux-um@lists.infradead.org
 help / color / mirror / Atom feed
From: Hongbo Li <lihongbo22@huawei.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: <oe-kbuild@lists.linux.dev>, <richard@nod.at>,
	<anton.ivanov@cambridgegreys.com>, <johannes@sipsolutions.net>,
	<lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>,
	<linux-um@lists.infradead.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] hostfs: convert hostfs to use the new mount api
Date: Thu, 30 May 2024 19:47:52 +0800	[thread overview]
Message-ID: <49f5cd14-987f-4d72-8606-496fca08a708@huawei.com> (raw)
In-Reply-To: <df349a89-e638-41de-858b-04341d89774e@moroto.mountain>

Thanks for replying.

I will send the new patch marked with v2 later.

regards,
Hongbo Li

On 2024/5/23 18:43, Dan Carpenter wrote:
> On Fri, May 17, 2024 at 07:21:09PM +0800, Hongbo Li wrote:
>> Thanks for your attention, I have solved the warnings in the following patch
>> (the similar title: hostfs: convert hostfs to use the new mount API):
>>
>> https://lore.kernel.org/all/20240515025536.3667017-1-lihongbo22@huawei.com/
>>
>> or
>>
>> https://patchwork.ozlabs.org/project/linux-um/patch/20240515025536.3667017-1-lihongbo22@huawei.com/
>>
>> It was strange that the kernel test robot did not send the results on the
>> new patch.
> 
> With uninitialized variable warnings, quite often Smatch is not the only
> or first checker to report the bug so I normally search lore to see if
> it has already been fixed.  In this case there were no bug reports from
> Nathan Chancelor and the second version of the patch wasn't marked as a
> v2 and there was no note explaining it like:
> 
> ---
> v2: fixed uninitialized variable warning
> 
> So it wasn't immediately clear that it had been fixed already.
> https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
> 
> regards,
> dan carpenter
> 


  reply	other threads:[~2024-05-30 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 12:41 [PATCH] hostfs: convert hostfs to use the new mount api Hongbo Li
2024-05-13 15:37 ` kernel test robot
2024-05-17 11:01 ` Dan Carpenter
2024-05-17 11:21   ` Hongbo Li
2024-05-23 10:43     ` Dan Carpenter
2024-05-30 11:47       ` Hongbo Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-15  2:55 [PATCH] hostfs: convert hostfs to use the new mount API Hongbo Li

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=49f5cd14-987f-4d72-8606-496fca08a708@huawei.com \
    --to=lihongbo22@huawei.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=dan.carpenter@linaro.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    --cc=richard@nod.at \
    /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