All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the f2fs tree
Date: Wed, 5 Nov 2014 11:58:58 +1100	[thread overview]
Message-ID: <20141105115858.047a7a60@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

Hi Jaegeuk,

After merging the f2fs tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

fs/f2fs/data.c: In function 'f2fs_write_begin':
fs/f2fs/data.c:960:19: error: 'fi' undeclared (first use in this function)
    set_inode_flag(fi, FI_DATA_EXIST);
                   ^

Caused by commit 2bac4643efc1 ("f2fs: revisit inline_data to avoid data
races and potential bugs").

I have used the f2fs tree from next-20141104 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-11-05  0:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  0:58 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-23  1:11 linux-next: build failure after merge of the f2fs tree 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
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=20141105115858.047a7a60@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jaegeuk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.