linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.32
Date: Wed, 28 Aug 2002 09:35:39 +0100	[thread overview]
Message-ID: <20020828093539.A22004@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020828061827.GB27967@lug-owl.de>; from jbglaw@lug-owl.de on Wed, Aug 28, 2002 at 08:18:27AM +0200

On Wed, Aug 28, 2002 at 08:18:27AM +0200, Jan-Benedict Glaw wrote:
> On Tue, 2002-08-27 20:54:30 -0000, Gabor Z. Papp <gzp@myhost.mynet>
> wrote in message <6e0.3d6be706.b5d05@gzp1.gzp.hu>:
> >   gcc -Wp,-MD,./.8250.o.d -D__KERNEL__ -I/usr/src/linux-2.5.32-gzp3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DMODULE -include /usr/src/linux-2.5.32-gzp3/include/linux/modversions.h   -DKBUILD_BASENAME=8250 -DEXPORT_SYMTAB  -c -o 8250.o 8250.c
> > In file included from 8250.c:34:
> > /usr/src/linux-2.5.32-gzp3/include/linux/serialP.h:50: field `icount' has incomplete type
> 
> Header file problem. In serialP.h, right at the beginning, there's a
> version check, which unfortunately is in wrong direction. No sources
> available, no patch...

It generally helps to search the list archives:

http://marc.theaimsgroup.com/?l=linux-kernel&m=102833316026209&w=2

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2002-08-28  8:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:47 Linux v2.5.32 Linus Torvalds
2002-08-27 20:22 ` Stephane Wirtel
2002-08-27 20:36   ` Thunder from the hill
2002-08-27 20:48     ` Stephane Wirtel
2002-08-27 20:54   ` Gabor Z. Papp
2002-08-28  6:18     ` Jan-Benedict Glaw
2002-08-28  7:41       ` Edward Coffey
2002-08-28  8:35       ` Russell King [this message]
2002-08-27 20:43 ` Udo A. Steinberg
2002-08-27 20:47   ` Andre Hedrick
2002-08-27 20:47   ` Alexander Viro
2002-08-27 22:35     ` Alan Cox
2002-08-28  2:07       ` [PATCH] " Alexander Viro
2002-08-28  1:21     ` Arador
2002-08-28  2:17       ` Alexander Viro
2002-08-27 22:28 ` Chris Funderburg (at home)
2002-08-28  7:31 ` Linux v2.5.32 - some menuconfig oddities Helge Hafting
2002-08-28  7:43   ` Gabor Kerenyi
2002-08-28  8:14 ` Linux v2.5.32 Edward Coffey
2002-08-28  8:17   ` Writing files to remote storage Kevin Liao
2002-08-28 14:18     ` Alan Cox
2002-08-28 13:00 ` 2.5.32 doesn't beep? Mikael Pettersson
2002-08-28 13:05   ` Vojtech Pavlik
2002-08-28 13:12     ` Mikael Pettersson
2002-08-28 13:58     ` Gerhard Mack
2002-08-28 14:33       ` Jos Hulzink
2002-08-28 14:49       ` Vojtech Pavlik
2002-08-28 20:04     ` Mikael Pettersson
2002-08-28 20:30       ` Vojtech Pavlik
2002-08-29  8:41         ` Gerd Knorr
2002-08-28 17:21 ` Linux v2.5.32 Adrian Bunk
2002-08-31 16:54 ` Linux v2.5.32 (Config options to have a working keyboard) Axel Siebenwirth
2002-08-27 23:50 Linux v2.5.32 Michel Eyckmans (MCE)
2002-08-28  0:43 rwhron
2002-08-28  1:15 ` Andre Hedrick
2002-08-28  2:21   ` Alexander Viro

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=20020828093539.A22004@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).