Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>,
	linux@cthulhu.engr.sgi.com
Subject: Re: kernel sources?
Date: Thu, 13 Jan 2000 01:20:33 +0100	[thread overview]
Message-ID: <20000113012033.A29273@uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.4.05.10001120953200.29324-100000@callisto.of.borg>

On Wed, Jan 12, 2000 at 09:57:41AM +0100, Geert Uytterhoeven wrote:

> Thanks! But unfortunately it doesn't fix all problems:
> 
> serial.c: In function `line_info':
> serial.c:3078: warning: long unsigned int format, unsigned int arg (arg 5)
> serial.c: In function `autoconfig':
> serial.c:3430: `ASYNC_IOC3' undeclared (first use this function)
> serial.c:3430: (Each undeclared identifier is reported only once
> serial.c:3430: for each function it appears in.)
> serial.c: In function `rs_init':
> serial.c:3999: `ASYNC_IOC3' undeclared (first use this function)
> serial.c:4015: warning: long unsigned int format, unsigned int arg (arg 4)
> 
> I think some #ifdef CONFIG_SGI_IP27/#endif is missing there.

Thanks for reporting!  What's actually missing is the definition of this
flag in include/linux/serial.h.

  Ralf

  reply	other threads:[~2000-01-13  0:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-11  9:53 kernel sources? Geert Uytterhoeven
2000-01-11 18:47 ` Harald Koerfgen
2000-01-12  8:57   ` Geert Uytterhoeven
2000-01-13  0:20     ` Ralf Baechle [this message]
2000-01-12 16:19   ` Geert Uytterhoeven
     [not found] <Pine.LNX.4.05.10001130944010.3492-100000@callisto.of.borg>
2000-01-13 16:03 ` Geert Uytterhoeven
2000-01-14 11:32   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2000-01-15 17:28 Kevin D. Kissell
2000-01-16  1:20 ` Ralf Baechle
2000-01-16 12:32 ` Geert Uytterhoeven

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=20000113012033.A29273@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=Harald.Koerfgen@home.ivm.de \
    --cc=geert@linux-m68k.org \
    --cc=linux@cthulhu.engr.sgi.com \
    /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