All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>,
	Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org, netdev@vger.kernel.org
Subject: Re: [stable] build error with 2.6.27.6+reiser4+ehci-hub patch. ERROR: "mii_ethtool_gset" [drivers/net/r8169.ko] undefined!
Date: Thu, 13 Nov 2008 16:07:25 -0800	[thread overview]
Message-ID: <20081114000725.GC19644@kroah.com> (raw)
In-Reply-To: <200811140045.20166.volker.armin.hemmann@tu-clausthal.de>

On Fri, Nov 14, 2008 at 12:45:19AM +0100, Volker Armin Hemmann wrote:
> Hi,
> with my old config from 2.6.27.5 (which has the same patches) I get this 
> error:
> make all modules_install install
> <snip>
>   OBJCOPY arch/x86/boot/setup.bin
>   OBJCOPY arch/x86/boot/vmlinux.bin
>   HOSTCC  arch/x86/boot/tools/build
>   BUILD   arch/x86/boot/bzImage
> Root device is (9, 1)
> Setup is 11436 bytes (padded to 11776 bytes).
> System is 2180 kB
> CRC 54816509
> Kernel: arch/x86/boot/bzImage is ready  (#1)
>   Building modules, stage 2.
>   MODPOST 136 modules
> ERROR: "mii_ethtool_gset" [drivers/net/r8169.ko] undefined!
> make[1]: *** [__modpost] Fehler 1
> make: *** [modules] Fehler 2

Francois, this is due to your commit
38d501ca6eb1f05d238bef785e51ca71dbfe0115, in the release, which was a
backport of ccdffb9a88b2907b159538d7bfd6256621db4f84.

Care to look into this?

thanks,

greg k-h

  parent reply	other threads:[~2008-11-14  0:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 23:45 build error with 2.6.27.6+reiser4+ehci-hub patch. ERROR: "mii_ethtool_gset" [drivers/net/r8169.ko] undefined! Volker Armin Hemmann
2008-11-13 23:49 ` Volker Armin Hemmann
2008-11-14  0:07 ` Greg KH [this message]
2008-11-14  1:26   ` [stable] " Ben Hutchings
2008-11-14  4:07     ` Greg KH
2008-11-14  6:39       ` Volker Armin Hemmann

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=20081114000725.GC19644@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=stable@kernel.org \
    --cc=volker.armin.hemmann@tu-clausthal.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.