All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-serial@vger.kernel.org
Subject: Re: build #306 failed for 2.6.22-g8d9107e in undefined reference to `netif_carrier_on'
Date: Mon, 16 Jul 2007 14:35:23 -0500	[thread overview]
Message-ID: <1184614523.10967.1.camel@x2.microgate.com> (raw)
In-Reply-To: <200707152350.49174.toralf.foerster@gmx.de>

On Sun, 2007-07-15 at 23:50 +0200, Toralf Förster wrote:
> Hello,
> 
> the build with the attached .config failed, make ends with:
> ...
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `isr_io_pin':
> synclinkmp.c:(.text+0x43d27): undefined reference to `netif_carrier_on'
> synclinkmp.c:(.text+0x43d2e): undefined reference to `netif_carrier_off'
> drivers/built-in.o: In function `rx_get_frame':
> synclinkmp.c:(.text+0x44167): undefined reference to `__alloc_skb'
> synclinkmp.c:(.text+0x441ff): undefined reference to `skb_over_panic'
> synclinkmp.c:(.text+0x44265): undefined reference to `netif_rx'

I built with your .config and did not get these errors.
The build completed successfully.

--
Paul Fulghum
Microgate Systems, Ltd

-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2007-07-16 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 21:50 build #306 failed for 2.6.22-g8d9107e in undefined reference to `netif_carrier_on' Toralf Förster
2007-07-16 19:35 ` Paul Fulghum [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=1184614523.10967.1.camel@x2.microgate.com \
    --to=paulkf@microgate.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=toralf.foerster@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 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.