All of lore.kernel.org
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: build failure with mason/for-linus tree
Date: Tue, 1 Jul 2014 14:43:34 +0900	[thread overview]
Message-ID: <53B24A86.1050802@jp.fujitsu.com> (raw)

Hi Chris,

FYI, today I failed to build mason/for-linus tree as follows.

===============================================================================
...
/home/sat/src/linux-2.6/fs/btrfs/transaction.c: In function 'record_root_in_trans':
/home/sat/src/linux-2.6/fs/btrfs/transaction.c:293:3: error: implicit declaration of function 'smp_mb__before_atomic' [-Werror=implicit-function-declaration]
   smp_mb__before_atomic();
   ^
/home/sat/src/linux-2.6/fs/btrfs/transaction.c: In function 'commit_fs_roots':
/home/sat/src/linux-2.6/fs/btrfs/transaction.c:1065:4: error: implicit declaration of function 'smp_mb__after_atomic' [-Werror=implicit-function-declaration]
    smp_mb__after_atomic();
    ^
cc1: some warnings being treated as errors
...
===============================================================================

It can be solved by cherry-picking febdbfe.

===
commit febdbfe8a91ce0d11939d4940b592eb0dba8d663
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Thu Feb 6 18:16:07 2014 +0100

    arch: Prepare for smp_mb__{before,after}_atomic()
    
    Since the smp_mb__{before,after}*() ops are fundamentally dependent on
    how an arch can implement atomics it doesn't make sense to have 3
    variants of them. They must all be the same.
===

Thanks,
Satoru



             reply	other threads:[~2014-07-01  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  5:43 Satoru Takeuchi [this message]
2014-07-01 14:30 ` build failure with mason/for-linus tree Chris Mason
2014-07-01 23:41   ` Satoru Takeuchi
2014-07-02  9:22     ` Miao Xie

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=53B24A86.1050802@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=linux-btrfs@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.