public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: schierlm@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.17-rc1
Date: Mon, 3 Apr 2006 14:48:20 -0700	[thread overview]
Message-ID: <20060403214820.GB29414@kroah.com> (raw)
In-Reply-To: <20060403194727.GD5616@flint.arm.linux.org.uk>

On Mon, Apr 03, 2006 at 08:47:27PM +0100, Russell King wrote:
> On Mon, Apr 03, 2006 at 01:18:12PM +0200, Michael Schierl wrote:
> > Linus Torvalds wrote:
> > 
> > > For the rest of you, there's the tar-balls, patches, and full ChangeLog.
> > 
> > Does not build here:
> > 
> > [...]
> >   LD      arch/i386/lib/built-in.o
> >   CC      arch/i386/lib/bitops.o
> >   AS      arch/i386/lib/checksum.o
> >   CC      arch/i386/lib/delay.o
> >   AS      arch/i386/lib/getuser.o
> >   CC      arch/i386/lib/memcpy.o
> >   AS      arch/i386/lib/putuser.o
> >   CC      arch/i386/lib/strstr.o
> >   CC      arch/i386/lib/usercopy.o
> >   AR      arch/i386/lib/lib.a
> >   GEN     .version
> >   CHK     include/linux/compile.h
> >   UPD     include/linux/compile.h
> >   CC      init/version.o
> >   LD      init/built-in.o
> >   LD      .tmp_vmlinux1
> > kernel/built-in.o:(.data+0x758): undefined reference to `uevent_helper'
> > make: *** [.tmp_vmlinux1] Error 1
> 
> I've reported this bug several times but I seem to be getting absolutely
> no response.  So I submitted it to bugzilla.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=6306
> 
> Feel free to add your voice to that bug to try to get someone to fix it.
> I'm not hopeful though.

Sorry, I've been swamped with other issues this past week.  I'll fix
this later this week when I get the chance.

thanks,

greg k-h

  reply	other threads:[~2006-04-03 21:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060403180207.E849EE007A12@knarzkiste.dyndns.org>
2006-04-03  3:47 ` Linux 2.6.17-rc1 Linus Torvalds
2006-04-03  5:13   ` KAMEZAWA Hiroyuki
2006-04-03  7:38     ` Russell King
2006-04-03 11:18   ` Michael Schierl
2006-04-03 19:47     ` Russell King
2006-04-03 21:48       ` Greg KH [this message]
2006-04-06 14:27       ` Martin Michlmayr
2006-04-06 21:21         ` Michael Schierl
2006-04-03 13:33   ` Jim MacBaine
2006-04-03 16:24   ` Tomasz Torcz
     [not found]     ` <20060403191552.GA8568@kroah.com>
2006-04-04  6:50       ` Tomasz Torcz
2006-04-03 19:09   ` Ralf Hildebrandt
2006-04-04  3:25     ` Andrew Morton
2006-04-04  8:05       ` Ralf Hildebrandt
2006-04-04  8:44         ` Andrew Morton
2006-04-09 11:28           ` Ralf Hildebrandt
2006-04-08 21:10         ` Hans-Peter Jansen
2006-04-04 23:39       ` [FUN]Re: " Ingo Oeser
2006-04-08 20:09   ` Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter Ville Herva
2006-04-08 22:05     ` David S. Miller
2006-04-09  4:09     ` Patrick McHardy
2006-04-09  7:43       ` Ville Herva
2006-04-09 14:44         ` Ville Herva
2006-04-09 14:45           ` Ville Herva
2006-04-09 16:00             ` Nix
2006-04-09 16:23               ` Andre Tomt
2006-04-11 11:27                 ` Jan Engelhardt
2006-04-09 16:37               ` Patrick McHardy
2006-04-09 16:53                 ` Nix
2006-04-09 17:10                   ` Ville Herva
2006-04-11  9:03                 ` Harald Welte
2006-04-11 19:10               ` Bill Davidsen

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=20060403214820.GB29414@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schierlm@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox