From: Dominique Martinet <asmadeus@codewreck.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the v9fs tree
Date: Wed, 13 Jul 2022 10:06:10 +0900 [thread overview]
Message-ID: <Ys4agrex2lNG/CzE@codewreck.org> (raw)
In-Reply-To: <20220713110222.70ca5fc5@canb.auug.org.au>
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
next prev parent reply other threads:[~2022-07-13 1:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 1:02 linux-next: build failure after merge of the v9fs tree Stephen Rothwell
2022-07-13 1:06 ` Dominique Martinet [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 4:03 Stephen Rothwell
2022-12-05 4:10 ` Dominique Martinet
2022-12-05 4:55 ` Stephen Rothwell
2022-12-05 14:31 ` Christian Schoenebeck
2022-12-05 20:40 ` Christian Schoenebeck
2022-12-05 22:41 ` Dominique Martinet
2022-12-08 15:55 ` Christian Schoenebeck
2022-12-08 23:53 ` Dominique Martinet
2022-12-09 14:40 ` Christian Schoenebeck
2022-12-09 21:24 ` Dominique Martinet
2011-12-01 1:02 Stephen Rothwell
2011-12-01 16:57 ` Joe Perches
2011-02-22 0:53 Stephen Rothwell
2011-02-22 5:20 ` Venkateswararao Jujjuri (JV)
2011-02-22 5:30 ` Stephen Rothwell
2011-02-22 6:22 ` Venkateswararao Jujjuri (JV)
2011-02-22 14:57 ` Eric Van Hensbergen
2011-02-22 16:48 ` Venkateswararao Jujjuri (JV)
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=Ys4agrex2lNG/CzE@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).