From: David Sterba <dsterba@suse•cz>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: open list <linux-kernel@vger•kernel.org>,
lkft-triage@lists•linaro.org, regressions@lists•linux.dev,
linux-btrfs@vger•kernel.org,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Josef Bacik <josef@toxicpanda•com>,
David Sterba <dsterba@suse•com>, Chris Mason <clm@fb•com>,
Anders Roxell <anders.roxell@linaro•org>,
Arnd Bergmann <arnd@arndb•de>
Subject: Re: btrfs: super.c:416:25: error: 'ret' undeclared (first use in this function); did you mean 'net'?
Date: Wed, 29 Nov 2023 12:55:11 +0100 [thread overview]
Message-ID: <20231129115511.GP18929@twin.jikos.cz> (raw)
In-Reply-To: <CA+G9fYvbCBUCkt-NdJ7HCETCFrzMWGnjnRBjCsw39Z_aUOaTDQ@mail.gmail.com>
On Tue, Nov 28, 2023 at 05:55:51PM +0530, Naresh Kamboju wrote:
> Following x86 and i386 build regressions noticed on Linux next-20231128 tag.
>
> Build log:
> -----------
> fs/btrfs/super.c: In function 'btrfs_parse_param':
> fs/btrfs/super.c:416:25: error: 'ret' undeclared (first use in this
> function); did you mean 'net'?
> 416 | ret = -EINVAL;
> | ^~~
> | net
> fs/btrfs/super.c:416:25: note: each undeclared identifier is reported
> only once for each function it appears in
> fs/btrfs/super.c:417:25: error: label 'out' used but not defined
> 417 | goto out;
> | ^~~~
> make[5]: *** [scripts/Makefile.build:243: fs/btrfs/super.o] Error 1
Fixed in today's for-next snapshot, thanks.
prev parent reply other threads:[~2023-11-29 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:25 btrfs: super.c:416:25: error: 'ret' undeclared (first use in this function); did you mean 'net'? Naresh Kamboju
2023-11-29 7:08 ` Bagas Sanjaya
2023-11-29 8:59 ` Naresh Kamboju
2023-11-29 9:58 ` Bagas Sanjaya
2023-11-29 11:55 ` David Sterba [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=20231129115511.GP18929@twin.jikos.cz \
--to=dsterba@suse$(echo .)cz \
--cc=anders.roxell@linaro$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=clm@fb$(echo .)com \
--cc=dsterba@suse$(echo .)com \
--cc=josef@toxicpanda$(echo .)com \
--cc=linux-btrfs@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=regressions@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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