linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Zimny Lech <napohybelskurwysynom2010@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 4
Date: Tue, 5 Oct 2010 12:11:52 -0700	[thread overview]
Message-ID: <20101005191152.GA14151@suse.de> (raw)
In-Reply-To: <49602.216.212.242.109.1286305155.squirrel@xenotime.net>

On Tue, Oct 05, 2010 at 11:59:15AM -0700, Randy Dunlap wrote:
> 
> On Mon, October 4, 2010 10:48 pm, Zimny Lech wrote:
> > Hi,
> >
> >
> > 2010/10/4 Stephen Rothwell <sfr@canb.auug.org.au>:
> >
> >> Hi all,
> >>
> >>
> >> This tree is not as well tested as others since it was only built after
> >>  all the merges had been done.
> >
> > Randy said that he had already sent a patch for this
> >
> >
> > /home/test/linux-2.6/drivers/base/core.c: In function
> > 'get_device_parent':
> > /home/test/linux-2.6/drivers/base/core.c:634:3: error: 'block_class'
> > undeclared (first use in this function)
> > /home/test/linux-2.6/drivers/base/core.c:634:3: note: each undeclared
> > identifier is reported only once for each function it appears in
> > /home/test/linux-2.6/drivers/base/core.c: In function
> > 'device_add_class_symlinks':
> > /home/test/linux-2.6/drivers/base/core.c:723:2: error: 'block_class'
> > undeclared (first use in this function)
> > /home/test/linux-2.6/drivers/base/core.c: In function
> > 'device_remove_class_symlinks':
> > /home/test/linux-2.6/drivers/base/core.c:751:2: error: 'block_class'
> > undeclared (first use in this function) make[3]: *** [drivers/base/core.o]
> > Error 1
> > make[2]: *** [drivers/base] Error 2
> > make[1]: *** [drivers] Error 2
> > make: *** [sub-make] Error 2
> 
> 
> I sure did, but Greg may be backlogged or just ignoring it.

backlogged, I was in Tokyo last week, catching up now...

thanks,

greg k-h

      reply	other threads:[~2010-10-05 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  0:36 linux-next: Tree for October 4 Stephen Rothwell
2010-10-04  8:34 ` [-next: Oct 4] s390x build break (kernel/power/process.o) Sachin Sant
2010-10-04 20:31   ` Rafael J. Wysocki
2010-10-05  2:38 ` linux-next: Tree for October 4 Zimny Lech
2010-10-05  2:42 ` Zimny Lech
2010-10-05  5:48 ` Zimny Lech
2010-10-05 18:59   ` Randy Dunlap
2010-10-05 19:11     ` 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=20101005191152.GA14151@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=napohybelskurwysynom2010@gmail.com \
    --cc=rdunlap@xenotime.net \
    --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).