From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Mark Brown <broonie@kernel.org>
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 f2fs tree
Date: Tue, 11 Aug 2026 16:23:36 +0000 [thread overview]
Message-ID: <antMiIWwTOybmHu9@google.com> (raw)
In-Reply-To: <ansbnhNDd8s8Inc6@sirena.org.uk>
My bad. Somehow I missed to add a header. Now, it should work.
On 08/11, Mark Brown wrote:
> Hi all,
>
> After merging the f2fs tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> /tmp/next/build/fs/f2fs/inode.c:1065:6: error: call to undeclared function 'current_is_kswapd'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 1065 | if (current_is_kswapd()) {
> | ^
>
> Caused by commit
>
> 7451b3cd93b30 (f2fs: call __add_ino_entry out of the eviction path)
>
> I have used the tree from next-20260810 instead.
next prev parent reply other threads:[~2026-08-11 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 12:54 linux-next: build failure after merge of the f2fs tree Mark Brown
2026-08-11 16:23 ` Jaegeuk Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-23 1:11 Stephen Rothwell
2021-08-27 0:28 ` Stephen Rothwell
2021-06-23 0:49 Stephen Rothwell
2021-07-11 3:08 ` Stephen Rothwell
2020-11-03 1:31 Stephen Rothwell
2020-11-03 1:35 ` Jaegeuk Kim
2019-05-02 0:53 Stephen Rothwell
2019-05-02 3:42 ` Jaegeuk Kim
2018-01-17 23:04 Stephen Rothwell
2014-11-05 0:58 Stephen Rothwell
2013-08-27 1:41 Stephen Rothwell
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=antMiIWwTOybmHu9@google.com \
--to=jaegeuk@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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