From: Dan Carpenter via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Philip Li <philip.li@intel.com>
Cc: oe-kbuild@lists.linux.dev, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev,
Heming Zhao via Ocfs2-devel <ocfs2-devel@oss.oracle.com>,
lkp@intel.com
Subject: Re: [Ocfs2-devel] fs/ocfs2/super.c:1809 ocfs2_mount_volume() warn: missing error code 'status'
Date: Tue, 4 Apr 2023 18:03:58 +0300 [thread overview]
Message-ID: <c6304335-9b5f-4082-b804-e754cf77ce0c@kili.mountain> (raw)
In-Reply-To: <ZCw5Ucw5CS6nXosr@rli9-mobl>
On Tue, Apr 04, 2023 at 10:50:57PM +0800, Philip Li wrote:
> On Mon, Apr 03, 2023 at 02:20:55PM +0300, Dan Carpenter wrote:
> > Sorry, the kbuild bot is not supposed to send duplicate warnings. I
> > don't know why it was sent again...
>
> Sorry about this, we should ignore this commit in the bot. Now it is configured
> to avoid the false positive report.
>
Fantastic. Thanks, Philip!
regards,
dan carpenter
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2023-04-04 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 6:14 [Ocfs2-devel] fs/ocfs2/super.c:1809 ocfs2_mount_volume() warn: missing error code 'status' Dan Carpenter via Ocfs2-devel
2023-04-03 11:07 ` Joseph Qi via Ocfs2-devel
2023-04-03 11:20 ` Dan Carpenter via Ocfs2-devel
2023-04-04 14:50 ` Philip Li via Ocfs2-devel
2023-04-04 15:03 ` Dan Carpenter via Ocfs2-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-05 11:15 Dan Carpenter via Ocfs2-devel
2022-11-06 12:38 ` Joseph Qi via Ocfs2-devel
2022-11-07 7:52 ` Dan Carpenter via Ocfs2-devel
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=c6304335-9b5f-4082-b804-e754cf77ce0c@kili.mountain \
--to=ocfs2-devel@oss.oracle.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=philip.li@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).