From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: Eduardo Silva <edsiper@gmail.com>
Cc: sedat.dilek@gmail.com, 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 22:13:13 +0200 [thread overview]
Message-ID: <BANLkTimWZx+2BdtzVQfKk+fPAJ8eHRwF9Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinRJ12Jc4u1OpB67cc3T3Trhci3dw@mail.gmail.com>
On Sun, May 22, 2011 at 10:08 PM, Eduardo Silva <edsiper@gmail.com> wrote:
> oh, yep, it was in UM arch :)
I've already submitted a patch for UML.
fs/inode.c is not the only place which needs the prefetch stuff...
--
Thanks,
//richard
prev parent reply other threads:[~2011-05-22 20:13 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
2011-05-22 20:13 ` richard -rw- weinberger [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=BANLkTimWZx+2BdtzVQfKk+fPAJ8eHRwF9Q@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=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).