linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: [mmotm:master 189/272] fs/affs/affs.h:10:22: fatal error: amigaffs.h: No such file or directory
Date: Thu, 4 May 2017 09:05:31 +0800	[thread overview]
Message-ID: <201705040904.C30fkUsv%fengguang.wu@intel.com> (raw)

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   670376fbea66d7b33412edefc754d4867e26d515
commit: 696cc1169d5609cee552f0e43c322c178a704b60 [189/272] linux-next-git-rejects
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout 696cc1169d5609cee552f0e43c322c178a704b60
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   In file included from fs/affs/super.c:23:0:
>> fs/affs/affs.h:10:22: fatal error: amigaffs.h: No such file or directory
    #include "amigaffs.h"
                         ^
   compilation terminated.

vim +10 fs/affs/affs.h

0158de12 Fabian Frederick  2014-06-06   1  #ifdef pr_fmt
0158de12 Fabian Frederick  2014-06-06   2  #undef pr_fmt
0158de12 Fabian Frederick  2014-06-06   3  #endif
0158de12 Fabian Frederick  2014-06-06   4  
0158de12 Fabian Frederick  2014-06-06   5  #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
0158de12 Fabian Frederick  2014-06-06   6  
^1da177e Linus Torvalds    2005-04-16   7  #include <linux/types.h>
^1da177e Linus Torvalds    2005-04-16   8  #include <linux/fs.h>
^1da177e Linus Torvalds    2005-04-16   9  #include <linux/buffer_head.h>
c1d6a71a Andrew Morton     2017-05-03 @10  #include "amigaffs.h"
7d135a5d Matthias Kaehlcke 2008-07-25  11  #include <linux/mutex.h>
3dd84782 Artem Bityutskiy  2012-06-06  12  #include <linux/workqueue.h>
^1da177e Linus Torvalds    2005-04-16  13  
^1da177e Linus Torvalds    2005-04-16  14  /* Ugly macros make the code more pretty. */
^1da177e Linus Torvalds    2005-04-16  15  
^1da177e Linus Torvalds    2005-04-16  16  #define GET_END_PTR(st,p,sz)		 ((st *)((char *)(p)+((sz)-sizeof(st))))
^1da177e Linus Torvalds    2005-04-16  17  #define AFFS_GET_HASHENTRY(data,hashkey) be32_to_cpu(((struct dir_front *)data)->hashtable[hashkey])
^1da177e Linus Torvalds    2005-04-16  18  #define AFFS_BLOCK(sb, bh, blk)		(AFFS_HEAD(bh)->table[AFFS_SB(sb)->s_hashsize-1-(blk)])

:::::: The code at line 10 was first introduced by commit
:::::: c1d6a71a2ed24d4f6576954fc19c7fde5b44696c linux-next

:::::: TO: Andrew Morton <akpm@linux-foundation.org>
:::::: CC: Johannes Weiner <hannes@cmpxchg.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39323 bytes --]

                 reply	other threads:[~2017-05-04  1:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201705040904.C30fkUsv%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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