mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kristian Hogsberg <hogsberg@users.sourceforge.net>
To: Ben Collins <bcollins@debian.org>
Cc: Keith Owens <kaos@ocs.com.au>,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	linux-kernel@vger.kernel.org,
	Kristian Hogsberg <hogsberg@users.sourceforge.net>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: Announce: modutils 2.4.9 is available
Date: 26 Sep 2001 14:52:32 +0200	[thread overview]
Message-ID: <m3ite62jxr.fsf@dk20037170.bang-olufsen.dk> (raw)
In-Reply-To: <3BB12FA3.96460B90@eyal.emu.id.au> <25245.1001471598@kao2.melbourne.sgi.com> <20010925224841.O319@visi.net>
In-Reply-To: <20010925224841.O319@visi.net>

Ben Collins <bcollins@debian.org> writes:

> On Wed, Sep 26, 2001 at 12:33:18PM +1000, Keith Owens wrote:
> > On Wed, 26 Sep 2001 11:30:11 +1000, 
> > Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
> > >I just built and installed modutils-2.4.9.
> > >depmod: Unexpected value (20) in
> > >'/lib/modules/2.4.10/kernel/drivers/ieee1394/sbp2.o' for
> > >ieee1394_device_size
> > >        It is likely that the kernel structure has changed, if so then
> > >        you probably need a new version of modutils to handle this
> > >kernel.
> 
> Kernel 2.4.9/2.4.10 do not contain the latest changes to the ieee1394
> tree. I've been trying to push the patches to Linus, but he is real
> busy, so it may take some time. Maybe 2.4.11 :)

Yes, when I sent the patch to modutils, I expected the latest cvs
changes to make it into 2.4.10.  Hopefully they will be in 2.4.11.

Kristian



      reply	other threads:[~2001-09-26 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25  7:48 Keith Owens
2001-09-26  1:30 ` Eyal Lebedinsky
2001-09-26  2:33   ` Keith Owens
2001-09-26  2:48     ` Ben Collins
2001-09-26 12:52       ` Kristian Hogsberg [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=m3ite62jxr.fsf@dk20037170.bang-olufsen.dk \
    --to=hogsberg@users.sourceforge.net \
    --cc=bcollins@debian.org \
    --cc=eyal@eyal.emu.id.au \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®