From: Jens Axboe <axboe@kernel.dk>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 11 (block/mm/fs)
Date: Fri, 11 Mar 2011 20:18:48 +0100 [thread overview]
Message-ID: <4D7A7598.4020301@kernel.dk> (raw)
In-Reply-To: <20110311095325.10ec7383.randy.dunlap@oracle.com>
On 2011-03-11 18:53, Randy Dunlap wrote:
> On Fri, 11 Mar 2011 18:41:15 +1100 Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20110310:
>>
>> The block tree lost its build failure but gained another for which I
>> applied a patch.
>
>
> When CONFIG_BLOCK is not enabled:
>
> mm/filemap.c:1257: error: storage size of 'plug' isn't known
> mm/filemap.c:2450: error: storage size of 'plug' isn't known
> mm/readahead.c:112: error: storage size of 'plug' isn't known
> fs/aio.c:1625: error: storage size of 'plug' isn't known
Thanks Randy, I fixed it up.
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 91fa428..16a902f 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -1297,15 +1297,18 @@ static inline long nr_blockdev_pages(void)
return 0;
}
-static inline void blk_start_plug(struct list_head *list)
+struct blk_plug {
+};
+
+static inline void blk_start_plug(struct blk_plug *plug)
{
}
-static inline void blk_finish_plug(struct list_head *list)
+static inline void blk_finish_plug(struct blk_plug *plug)
{
}
-static inline void blk_flush_plug(struct task_struct *tsk)
+static inline void blk_flush_plug(struct task_struct *task)
{
}
--
Jens Axboe
prev parent reply other threads:[~2011-03-11 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 7:41 linux-next: Tree for March 11 Stephen Rothwell
2011-03-11 17:53 ` linux-next: Tree for March 11 (block/mm/fs) Randy Dunlap
2011-03-11 19:18 ` Jens Axboe [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=4D7A7598.4020301@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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.