public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah•com>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Kay Sievers <kay.sievers@vrfy•org>,
	linux-kernel@vger•kernel.org, linuxppc-dev@ozlabs•org,
	raisch@de•ibm.com, Olof Johansson <olof@lixom•net>,
	jgarzik@pobox•com
Subject: Re: 2.6.24-rc8-mm1 powerpc build errors
Date: Thu, 17 Jan 2008 14:00:07 -0800	[thread overview]
Message-ID: <20080117220007.GB12952@kroah.com> (raw)
In-Reply-To: <20080117113523.d802f991.akpm@linux-foundation.org>

On Thu, Jan 17, 2008 at 11:35:23AM -0800, Andrew Morton wrote:
> On Thu, 17 Jan 2008 13:06:39 -0600 Olof Johansson <olof@lixom•net> wrote:
> > powerpc_allyesconfig:
> > 
> > drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_add':
> > drivers/net/ehea/ehea_main.c:2812: error: 'struct device_driver' has no member named 'kobj'
> > drivers/net/ehea/ehea_main.c:2815: error: 'struct device_driver' has no member named 'kobj'
> > drivers/net/ehea/ehea_main.c:2818: error: 'struct device_driver' has no member named 'kobj'
> > drivers/net/ehea/ehea_main.c: In function 'ehea_driver_sysfs_remove':
> > drivers/net/ehea/ehea_main.c:2830: error: 'struct device_driver' has no member named 'kobj'
> 
> Looks like the driver tree wrecking ball failed to visit that driver.

Crap, I thought I fixed that one, but the patch never made it out...
I'll fix that tomorrow, sorry about that.

greg k-h

  reply	other threads:[~2008-01-17 21:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080117023514.9df393cf.akpm@linux-foundation.org>
2008-01-17 18:18 ` 2.6.24-rc8-mm1: powerpc: include/asm/nvram.h:62: error: field 'partition' has incomplete type Mariusz Kozlowski
2008-01-17 19:27   ` Andrew Morton
2008-01-17 19:06 ` 2.6.24-rc8-mm1 powerpc build errors Olof Johansson
2008-01-17 19:35   ` Andrew Morton
2008-01-17 22:00     ` Greg KH [this message]
2008-01-17 22:15 ` 2.6.24-rc8-mm1: powerpc oopses Mariusz Kozlowski
2008-01-17 22:51   ` Andrew Morton
2008-01-17 23:39     ` Matt Mackall
2008-01-18  0:05       ` Andrew Morton
2008-01-18  0:12         ` Matt Mackall
2008-01-18  0:29           ` Andrew Morton
2008-01-18  0:47             ` Matt Mackall
2008-01-18  1:07               ` Andrew Morton
2008-01-18  1:16                 ` Matt Mackall
2008-01-18 17:23               ` Mariusz Kozlowski
2008-01-18 17:33                 ` Matt Mackall
2008-01-18  7:09 ` 2.6.24-rc8-mm1 build failure on headers_check Kamalesh Babulal
2008-01-18  7:38   ` Andrew Morton
2008-01-18  8:36 ` 2.6.24-rc8-mm1 Kernel oops will running kernbench Kamalesh Babulal
2008-01-18  8:44   ` Andrew Morton
2008-01-18  9:01     ` Paul Mackerras
2008-01-18  9:34       ` Kamalesh Babulal
2008-01-18 10:19         ` Paul Mackerras
2008-01-18 15:41           ` Milton Miller
2008-01-18 10:26         ` Paul Mackerras
2008-01-18 10:44           ` Kamalesh Babulal
2008-01-18 10:54             ` Balbir Singh
2008-01-25  6:05           ` 2.6.24 Kernel oops will running kernbench regression from 2.6.24-rc8-mm1 Kamalesh Babulal

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=20080117220007.GB12952@kroah.com \
    --to=greg@kroah$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=jgarzik@pobox$(echo .)com \
    --cc=kay.sievers@vrfy$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=olof@lixom$(echo .)net \
    --cc=raisch@de$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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