public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Erik Andersen <andersen@codepoet.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	bcollins@debian.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix 2.4.x ieee1394
Date: Sun, 29 Dec 2002 18:43:52 +0100	[thread overview]
Message-ID: <20021229174351.GA6114@fs.tum.de> (raw)
In-Reply-To: <20021229164409.GA5416@codepoet.org>

On Sun, Dec 29, 2002 at 09:44:09AM -0700, Erik Andersen wrote:
> On Sun Dec 29, 2002 at 04:38:21PM +0100, Adrian Bunk wrote:
> > When I try 2.4.21-pre2 with your patch and the IEEE 1394 options you 
> > mention in your mail _nothing_ gets built inside the drivers/ieee1394 
> > directory and the error message at the final linking is:
> > 
> > <--  snip  -->
> > 
> > ...
> >         -o vmlinux
> > ld: cannot open drivers/ieee1394/ieee1394.o: No such file or directory
> > make: *** [vmlinux] Error 1
> > 
> > <--  snip  -->
> > 
> > 
> > How did you manage to get a kernel that actually compiles?
> > 
> 
> Sorry about that.  I missed a spot.  Here is the full fix:
>...

Thanks, I can confirm that this patch fixes it.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      parent reply	other threads:[~2002-12-29 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200212172033.gBHKX6A32611@hera.kernel.org>
2002-12-22 11:26 ` [PATCH] fix 2.4.x ieee1394 Erik Andersen
2002-12-22 14:01   ` Ben Collins
2002-12-29 15:38   ` Adrian Bunk
2002-12-29 16:44     ` Erik Andersen
2002-12-29 16:52       ` Ben Collins
2002-12-31 15:19         ` Kai Germaschewski
2002-12-29 17:43       ` Adrian Bunk [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=20021229174351.GA6114@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=andersen@codepoet.org \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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