From: Randy Dunlap <randy.dunlap@oracle.com>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
LKML <linux-kernel@vger.kernel.org>,
axboe@kernel.dk
Subject: Re: [linux-next] fs/ocfs2/file.c:201: error: ‘BLKDEV_IFL_WAIT’ undeclared (first use in this function)
Date: Fri, 17 Sep 2010 10:18:28 -0700 [thread overview]
Message-ID: <20100917101828.813e4515.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTimeZyZstBR4ZRxJg3OaP_aibLqQtYw2dTJ7cq7c@mail.gmail.com>
On Fri, 17 Sep 2010 17:36:43 +0200 Sedat Dilek wrote:
> Hi,
>
> I pulled linux-2.6-block/for-next into mainline.
>
> The build breaks, the issue is known [1] (but I didnt see a patch):
Just a verbal patch, yes.
> [ build.log ]
> ...
> /home/sd/src/linux-2.6/linux-2.6.36-rc4/debian/build/source_i386_none/fs/ocfs2/file.c:201:
> error: ‘BLKDEV_IFL_WAIT’ undeclared (first use in this function)
> /home/sd/src/linux-2.6/linux-2.6.36-rc4/debian/build/source_i386_none/fs/ocfs2/file.c:201:
> error: (Each undeclared identifier is reported only once
> /home/sd/src/linux-2.6/linux-2.6.36-rc4/debian/build/source_i386_none/fs/ocfs2/file.c:201:
> error: for each function it appears in.)
> /home/sd/src/linux-2.6/linux-2.6.36-rc4/debian/build/source_i386_none/fs/ocfs2/file.c:201:
> error: too many arguments to function ‘blkdev_issue_flush’
> CC [M] net/rxrpc/ar-error.o
> CC [M] drivers/scsi/scsi_error.o
> make[3]: *** [sub-make] Error 2
> make[2]: *** [all] Error 2
>
> Regards,
> - Sedat -
>
> [1] http://www.spinics.net/lists/linux-next/msg11970.html
>
> P.S.: Is there an email-address for linux-next (did not see in MAINTAINERS)?
http://vger.kernel.org/vger-lists.html#linux-next
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-09-17 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 15:36 Sedat Dilek
2010-09-17 17:18 ` Randy Dunlap [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=20100917101828.813e4515.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
/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
all inboxes | Powered by JetHome®