linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Philippe Roussel <p.o.roussel@free.fr>,
	linux-next@vger.kernel.org,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: linux-next 20080526 build failure with CONFIG_BLOCK=y and CONFIG_PROC_FS is not set
Date: Tue, 27 May 2008 20:57:40 -0700	[thread overview]
Message-ID: <20080528035740.GA7845@kroah.com> (raw)
In-Reply-To: <20080528123416.c0bf2a0a.sfr@canb.auug.org.au>

On Wed, May 28, 2008 at 12:34:16PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Mon, 26 May 2008 09:22:24 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> >
> > On Mon, 26 May 2008 11:28:14 +0200 Philippe Roussel wrote:
> > 
> > > I got this
> > > 
> > >   CC      block/genhd.o
> > > block/genhd.c: In function 'diskstats_start':
> > > block/genhd.c:555: error: 'find_start' undeclared (first use in this
> > > function)
> > > block/genhd.c:555: error: (Each undeclared identifier is reported only
> > > once
> > > block/genhd.c:555: error: for each function it appears in.)
> > > 
> > > while building the following config
> > 
> > I sent a patch for this last Friday:
> >   http://lkml.org/lkml/2008/5/23/255
> 
> Did you see this?

Ah, no, sorry, I totally missed it.

Randy, I've put your patch in my queue, in a place that keeps the build
error from ever happening.  Thanks for pointing it out.

greg k-h

      reply	other threads:[~2008-05-28  4:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26  9:28 linux-next 20080526 build failure with CONFIG_BLOCK=y and CONFIG_PROC_FS is not set Philippe Roussel
2008-05-26 16:22 ` Randy Dunlap
2008-05-28  2:34   ` Stephen Rothwell
2008-05-28  3:57     ` Greg KH [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=20080528035740.GA7845@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=p.o.roussel@free.fr \
    --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 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).