public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Joern Engel <joern@logfs.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	logfs@logfs.org
Subject: Re: linux-next: Tree for April 28 (logfs)
Date: Wed, 5 May 2010 09:20:20 -0700	[thread overview]
Message-ID: <20100505092020.66a461fa.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100428085604.0566092a.randy.dunlap@oracle.com>

On Wed, 28 Apr 2010 08:56:04 -0700 Randy Dunlap wrote:

> 
> When CONFIG_BLOCK is not enabled:
> 
> fs/logfs/super.c:142: error: implicit declaration of function 'bdev_get_queue'
> fs/logfs/super.c:142: error: invalid type argument of '->' (have 'int')


Still have this build error in linux-next-May 5-2010.

[and L:      logfs@logfs.org
is moderated for non-subscribers]

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-05-05 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  6:43 linux-next: Tree for April 28 Stephen Rothwell
2010-04-28 15:56 ` linux-next: Tree for April 28 (logfs) Randy Dunlap
2010-05-05 16:20   ` Randy Dunlap [this message]
2010-05-05 20:35     ` Jörn Engel
2010-05-09  6:20       ` Ingo Molnar
2010-05-17  3:48         ` linux-next -> 2.6.34: " Randy Dunlap
2010-05-17 19:31           ` Jörn Engel
2010-05-18  0:40             ` Ingo Molnar
2010-05-17 19:25         ` linux-next: " Jörn Engel
2010-04-28 17:33 ` [PATCH -next] infiniband: fix cxgb4 printk format warnings Randy Dunlap
2010-05-05 18:57   ` Roland Dreier

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=20100505092020.66a461fa.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=logfs@logfs.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