Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] DEC: Fix modpost warning.
Date: Tue, 10 Jul 2007 14:04:09 +0100	[thread overview]
Message-ID: <20070710130409.GA14723@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0707101401001.18036@blysk.ds.pg.gda.pl>

On Tue, Jul 10, 2007 at 02:07:21PM +0100, Maciej W. Rozycki wrote:
> From: "Maciej W. Rozycki" <macro@linux-mips.org>
> Date: Tue, 10 Jul 2007 14:07:21 +0100 (BST)
> To: linux-mips@linux-mips.org
> Subject: Re: [MIPS] DEC: Fix modpost warning.
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> On Tue, 10 Jul 2007, linux-mips@linux-mips.org wrote:
> 
> >   LD      vmlinux
> >   SYSMAP  System.map
> >   SYSMAP  .tmp_System.map
> >   MODPOST vmlinux
> > WARNING: drivers/built-in.o(.data+0x2480): Section mismatch: reference to .init.text: (between 'sercons' and 'ds_parms')
> > 
> > Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
> > 
> > ---
> > 
> >  drivers/tc/zs.c |    6 +++---
> >  1 files changed, 3 insertions(+), 3 deletions(-)
> 
>  It looks like a bogus warning -- I presume it comes from a reference from 
> "sercons" to serial_console_setup() -- but the driver is going away, so I 
> could not care less...

Yes, the root cause was the reference to serial_console_setup.  It's hard
to teach modpost that this reference is bogus so I fixed the driver instead.
Other console drivers had the same issue.

  Ralf

  reply	other threads:[~2007-07-10 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S20022577AbXGJLug/20070710115036Z+13637@ftp.linux-mips.org>
2007-07-10 13:07 ` [MIPS] DEC: Fix modpost warning Maciej W. Rozycki
2007-07-10 13:04   ` Ralf Baechle [this message]
2007-07-10 14:10     ` Atsushi Nemoto
2007-07-10 14:37     ` Maciej W. Rozycki
2007-07-10 23:20       ` Ralf Baechle

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=20070710130409.GA14723@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox