From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <sfr@canb.auug.org.au>
Cc: <kuniyu@amazon.com>, <linux-kernel@vger.kernel.org>,
<linux-next@vger.kernel.org>, <trond.myklebust@hammerspace.com>,
<trondmy@gmail.com>
Subject: Re: linux-next: build failure after merge of the nfs tree
Date: Thu, 4 Apr 2024 16:08:17 -0700 [thread overview]
Message-ID: <20240404230817.62526-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20240405095341.3a9f0d95@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 5 Apr 2024 09:53:41 +1100
> Hi all,
>
> After merging the nfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> fs/nfs/inode.c: In function 'nfs_net_init':
> fs/nfs/inode.c:2434:13: error: assignment to 'int' from 'struct proc_dir_entry *' makes integer from pointer without a cast [-Werror=int-conversion]
> 2434 | err = rpc_proc_register(net, &nn->rpcstats);
> | ^
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> f290a586e31f ("nfs: Handle error of rpc_proc_register() in nfs_net_init().")
>
> I have used the nfs tree from next-20240404 for today.
Sorry, I posted v2 of the patch.
https://lore.kernel.org/linux-nfs/20240404221200.52876-1-kuniyu@amazon.com/
next prev parent reply other threads:[~2024-04-04 23:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 22:53 linux-next: build failure after merge of the nfs tree Stephen Rothwell
2024-04-04 23:08 ` Kuniyuki Iwashima [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-27 0:58 Stephen Rothwell
2016-06-27 15:44 ` Trond Myklebust
2016-06-14 0:48 Stephen Rothwell
2016-05-19 0:58 Stephen Rothwell
2016-05-19 12:06 ` Trond Myklebust
2016-05-19 17:30 ` Anna Schumaker
2016-01-08 0:14 Stephen Rothwell
2016-01-08 0:15 ` Trond Myklebust
2015-08-18 0:56 Stephen Rothwell
2015-08-19 0:05 ` Stephen Rothwell
2015-08-19 0:15 ` Drokin, Oleg
2015-08-23 23:16 ` Stephen Rothwell
2015-08-24 14:17 ` Trond Myklebust
2015-08-24 14:48 ` Oleg Drokin
2014-09-15 7:04 Stephen Rothwell
2014-09-15 17:07 ` Christoph Hellwig
2013-11-19 0:01 Stephen Rothwell
2012-10-02 0:39 Stephen Rothwell
2012-10-02 1:08 ` Myklebust, Trond
2012-05-16 2:49 Stephen Rothwell
2012-05-16 17:47 ` Myklebust, Trond
2012-03-05 0:45 Stephen Rothwell
2012-03-05 1:58 ` Myklebust, Trond
2012-01-23 0:39 Stephen Rothwell
2012-01-23 18:13 ` Trond Myklebust
2012-01-23 21:10 ` Stephen Rothwell
2011-05-27 2:08 Stephen Rothwell
2011-05-12 1:12 Stephen Rothwell
2011-05-12 15:11 ` Trond Myklebust
2011-03-11 0:22 Stephen Rothwell
2011-03-08 1:07 Stephen Rothwell
2011-03-08 18:58 ` Trond Myklebust
2010-10-21 0:38 Stephen Rothwell
2010-10-21 14:33 ` Trond Myklebust
2010-03-22 0:26 Stephen Rothwell
2010-03-22 9:49 ` Trond Myklebust
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=20240404230817.62526-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@hammerspace.com \
--cc=trondmy@gmail.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