linux-kernel - Re: linux-next: build failure after merge of the v9fs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Ys4agrex2lNG/CzE@codewreck.org>
Date:   Wed, 13 Jul 2022 10:06:10 +0900
From:   Dominique Martinet <asmadeus@...ewreck.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the v9fs tree

Stephen Rothwell wrote on Wed, Jul 13, 2022 at 11:02:22AM +1000:
> After merging the v9fs tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> net/9p/trans_fd.c:275:12: error: 'failme' defined but not used [-Werror=unused-variable]
>   275 | static int failme;
>       |            ^~~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   c249fb4f9193 ("9p: roll p9_tag_remove into p9_req_put")
> 
> I have used the v9fs tree from next-20220712 for today.

Sorry, fixed in my tree.

That can wait tomorrow.

--
Dominique