From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, axboe@kernel.dk
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 6 (block git tree)
Date: Fri, 06 Aug 2010 12:06:00 -0700 [thread overview]
Message-ID: <4C5C5D18.6050905@oracle.com> (raw)
In-Reply-To: <20100806120456.5eca82b7.randy.dunlap@oracle.com>
On 08/06/10 12:04, Randy Dunlap wrote:
> On Fri, 6 Aug 2010 13:27:58 +1000 Stephen Rothwell wrote:
>
>> Hi all,
>>
>> As the merge window is open, please do not add 2.6.37 material to your
>> linux-next included trees until after 2.6.36-rc1.
>>
>> Changes since 20100805:
>>
>> The block tree lost its build failure and a conflict.
>
>
> Lots of source files now need <linux/blk_types.h>:
>
> mm/filemap.c:2164: error: 'REQ_WRITE' undeclared
> fs/read_write.c:362: error: 'REQ_WRITE' undeclared
> fs/splice.c:1108: error: 'REQ_WRITE' undeclared
> fs/aio.c:1496: error: 'REQ_WRITE' undeclared
> drivers/memstick/core/memstick.c:272: error: 'REQ_WRITE' undeclared
> drivers/memstick/host/tifm_ms.c:218: error: 'REQ_WRITE' undeclared
> drivers/memstick/host/jmb38x_ms.c:333: error: 'REQ_WRITE' undeclared
> drivers/staging/spectra/ffsport.c:277: error: 'REQ_TYPE_LINUX_BLOCK' undeclared
> fs/compat.c:1274: error: 'REQ_WRITE' undeclared
Sorry, I see that this has already been fixed.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-06 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 3:27 linux-next: Tree for August 6 Stephen Rothwell
2010-08-06 18:53 ` linux-next: Tree for August 6 (kgdboc) Randy Dunlap
2010-08-06 20:00 ` Jason Wessel
2010-08-06 21:03 ` rdunlap
2010-08-06 19:04 ` linux-next: Tree for August 6 (block git tree) Randy Dunlap
2010-08-06 19:06 ` Randy Dunlap [this message]
2010-08-10 15:37 ` Randy Dunlap
2010-08-10 15:51 ` Jens Axboe
2010-08-10 15:54 ` Randy Dunlap
2010-08-10 15:56 ` Jens Axboe
2010-08-10 15:59 ` Randy Dunlap
2010-08-10 16:07 ` Jens Axboe
2010-08-10 16:11 ` Randy Dunlap
2010-08-10 16:14 ` Jens Axboe
2010-08-10 16:34 ` 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=4C5C5D18.6050905@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).