From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Jens Axboe <axboe@kernel•dk>
Cc: 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 09:53:25 -0800 [thread overview]
Message-ID: <20110311095325.10ec7383.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110311184115.33404b77.sfr@canb.auug.org.au>
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
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-03-11 17:54 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 ` Randy Dunlap [this message]
2011-03-11 19:18 ` linux-next: Tree for March 11 (block/mm/fs) Jens Axboe
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=20110311095325.10ec7383.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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