All of lore.kernel.org
 help / color / mirror / Atom feed
From: trem <trem@zarb.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
	Tom Rini <trini@kernel.crashing.org>,
	linux-kernel@vger.kernel.org
Subject: Re: dependance loop on 2.6.14-rc1-mm1
Date: Sat, 17 Sep 2005 14:28:34 +0200	[thread overview]
Message-ID: <432C0BF2.6020406@zarb.org> (raw)
In-Reply-To: <20050917115138.GA17589@flint.arm.linux.org.uk>

Hi

I've done a little test, I've remove this line from serial_core.c

+#ifdef CONFIG_KGDB
+       {
+               extern int kgdb_irq;
+
+               if (port->irq == kgdb_irq)
+                       return;
+       }
+#endif


and now the make modules_install works fine.

thanks for the help,
trem



Russell King a écrit :

>On Sat, Sep 17, 2005 at 01:40:54PM +0200, trem wrote:
>  
>
>>I've tried to compile a 2.6.14-rc1-mm1 on my amd64. When I do the make 
>>modules_install,
>>I have this warning:
>>
>>WARNING: Loop detected:
>>/lib/modules/2.6.14-rc1-mm1/kernel/drivers/serial/8250.ko needs 
>>serial_core.ko which needs 8250.ko again!
>>    
>>
>
>This looks suspicious.  8250 should need serial_core, but there's no
>way in hell serial_core should require 8250. 
>
>Seems to be caused by the kgdb patches, which add the following to
>serial_core:
>
>+#ifdef CONFIG_KGDB
>+       {
>+               extern int kgdb_irq;
>+
>+               if (port->irq == kgdb_irq)
>+                       return;
>+       }
>+#endif
>+
>
>and kgdb_irq comes from the 8250 module.
>
>Tom, can this dependency be solved before kgdb goes near mainline
>please?
>
>  
>



  reply	other threads:[~2005-09-17 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 11:40 dependance loop on 2.6.14-rc1-mm1 trem
2005-09-17 11:51 ` Russell King
2005-09-17 12:28   ` trem [this message]
2005-09-17 15:48   ` Tom Rini

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=432C0BF2.6020406@zarb.org \
    --to=trem@zarb.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=trini@kernel.crashing.org \
    /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.