From: Eduardo Silva <edsiper@gmail.com>
To: sedat.dilek@gmail.com
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: add missing prefetch header to inode.c
Date: Sun, 22 May 2011 16:08:54 -0400 [thread overview]
Message-ID: <BANLkTinRJ12Jc4u1OpB67cc3T3Trhci3dw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin6=3rpchVFHi9P=6Cp31uL=vMM0w@mail.gmail.com>
oh, yep, it was in UM arch :)
On Sun, May 22, 2011 at 4:04 PM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> On Sun, May 22, 2011 at 9:34 PM, Eduardo Silva <edsiper@gmail.com> wrote:
>> inode.c fails in the compilation process due to the missing
>> include of linux/prefetch.h.
>>
>> Signed-off-by: Eduardo Silva <edsiper@gmail.com>
>> ---
>> fs/inode.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/fs/inode.c b/fs/inode.c
>> index 33c963d..c77081f 100644
>> --- a/fs/inode.c
>> +++ b/fs/inode.c
>> @@ -26,6 +26,7 @@
>> #include <linux/posix_acl.h>
>> #include <linux/ima.h>
>> #include <linux/cred.h>
>> +#include <linux/prefetch.h>
>> #include "internal.h"
>>
>> /*
>> --
>> 1.7.4.1
>>
>
> Just FYI:
> "fs: add missing prefetch.h include" is in Linus tree [1].
>
> - Sedat -
>
> [1] http://git.us.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9ce6e0be0626a5de2aca8b769a4aa57086257156
>
--
Eduardo Silva
http://edsiper.linuxchile.cl
http://www.monkey-project.com
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-22 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 19:34 [PATCH] fs: add missing prefetch header to inode.c Eduardo Silva
2011-05-22 19:51 ` richard -rw- weinberger
2011-05-22 20:04 ` Sedat Dilek
2011-05-22 20:08 ` Eduardo Silva [this message]
2011-05-22 20:13 ` richard -rw- weinberger
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=BANLkTinRJ12Jc4u1OpB67cc3T3Trhci3dw@mail.gmail.com \
--to=edsiper@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).