From: Laura Abbott <lauraa@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: Re: [next:master 103/113] include/linux/blkdev.h:25:29: fatal error: asm/scatterlist.h: No such file or directory
Date: Wed, 16 Apr 2014 09:17:22 -0700 [thread overview]
Message-ID: <534EAD12.3090602@codeaurora.org> (raw)
In-Reply-To: <534e2a6e.Ldm85XovY2CX2Ogp%fengguang.wu@intel.com>
On 4/15/2014 11:59 PM, kbuild test robot wrote:
> In file included from init/main.c:75:0:
>>> >> include/linux/blkdev.h:25:29: fatal error: asm/scatterlist.h: No such file or directory
> #include <asm/scatterlist.h>
> ^
> compilation terminated.
The following patch fixes the compile breakage. For my own knowledge, why did this break in
this particular way?
---- 8< -----
prev parent reply other threads:[~2014-04-16 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 6:59 [next:master 103/113] include/linux/blkdev.h:25:29: fatal error: asm/scatterlist.h: No such file or directory kbuild test robot
2014-04-16 16:17 ` Laura Abbott [this message]
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=534EAD12.3090602@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jdike@addtoit.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).