From: Yujie Liu <yujie.liu@intel.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Qu Wenruo <wqu@suse.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>, <dsterba@suse.com>,
<nathan@kernel.org>, "Nick Desaulniers" <ndesaulniers@google.com>,
<linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] btrfs: Initialize ret to 0 in scrub_simple_mirror()
Date: Tue, 1 Mar 2022 09:55:06 +0800 [thread overview]
Message-ID: <1ebaefbc-ef9e-3060-3572-5ee560b7c4de@intel.com> (raw)
In-Reply-To: <e94b337b-38ea-8705-4dd7-c09ac6b98ec0@intel.com>
Hi Souptick,
On 2/25/2022 18:02, Yujie Liu wrote:
> Hi Souptick,
>
> On 2/25/2022 13:16, Souptick Joarder wrote:
>> On Thu, Feb 24, 2022 at 3:18 PM Yujie Liu <yujie.liu@intel.com> wrote:
>>>
>>> Souptick, could you help to provide the original report by link or attachment?
>>
>> https://marc.info/?l=linux-mm&m=164487037605771&w=2
>>
>
> this link is a notification mail of build status, but not a formal report,
> so there may be many false alerts in this mail, please ignore them.
>
Sorry, previous info was not accurate, here are some updates:
In a build notification mail(such as above link https://marc.info/?l=linux-mm&m=164487037605771&w=2),
there is a hint line like:
possible Error/Warning in current branch (please contact us if interested):
the errors/warnings in this section are not fully verified like the ones generated
by static analysis tools.
We will make this line clearer to mention that they could be false positives.
Thanks,
Yujie
prev parent reply other threads:[~2022-03-01 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 14:46 [PATCH] btrfs: Initialize ret to 0 in scrub_simple_mirror() Souptick Joarder
2022-02-21 0:15 ` Qu Wenruo
2022-02-22 7:50 ` Souptick Joarder
2022-02-22 8:04 ` Qu Wenruo
2022-02-22 8:09 ` Souptick Joarder
2022-02-24 9:48 ` Yujie Liu
2022-02-24 9:56 ` Qu Wenruo
2022-02-25 9:35 ` Yujie Liu
2022-02-25 5:16 ` Souptick Joarder
2022-02-25 10:02 ` Yujie Liu
2022-03-01 1:55 ` Yujie Liu [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=1ebaefbc-ef9e-3060-3572-5ee560b7c4de@intel.com \
--to=yujie.liu@intel.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=wqu@suse.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