From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
gregkh@suse.de
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
lud <linux-usb@vger.kernel.org>
Subject: Re: [PATCH -next] gadget: f_fs.c needs to include pagemap.h
Date: Tue, 11 May 2010 12:02:03 +0200 [thread overview]
Message-ID: <op.vcjctphf7p4s8u@pikus> (raw)
In-Reply-To: <20100510105136.eee3e58a.randy.dunlap@oracle.com>
On Mon, 10 May 2010 19:51:36 +0200, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Fix g_ffs build error, add a needed header file:
>
> drivers/usb/gadget/f_fs.c:1064:error: 'PAGE_CACHE_SIZE' undeclared (first use in this function)
> drivers/usb/gadget/f_fs.c:1065:error: 'PAGE_CACHE_SHIFT' undeclared (first use in this function)
> --- linux-next-20100510.orig/drivers/usb/gadget/f_fs.c
> +++ linux-next-20100510/drivers/usb/gadget/f_fs.c
> @@ -28,6 +28,7 @@
> /* #define VERBOSE_DEBUG */
> #include <linux/blkdev.h>
> +#include <linux/pagemap.h>
> #include <asm/unaligned.h>
> #include <linux/smp_lock.h>
Needles to say, this looks reasonable.
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
next prev parent reply other threads:[~2010-05-11 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 6:02 linux-next: Tree for May 10 Stephen Rothwell
2010-05-10 17:51 ` [PATCH -next] gadget: f_fs.c needs to include pagemap.h Randy Dunlap
2010-05-11 10:02 ` Michał Nazarewicz [this message]
2010-05-11 23:43 ` patch usb-gadget-f_fs.c-needs-to-include-pagemap.h.patch added to gregkh-2.6 tree gregkh
2010-05-10 17:53 ` [PATCH -next] staging: memrar depends on RAR_REGISTER Randy Dunlap
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=op.vcjctphf7p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.