All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Paul Fulghum <paulkf@microgate.com>
Cc: "Steven E. Woolard" <tuxq@tuxq.com>,
	linux-serial@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Bug?: 2.6.9-bk3
Date: Wed, 20 Oct 2004 08:59:18 +0100	[thread overview]
Message-ID: <20041020085918.B1047@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1098240366.5963.21.camel@at2.pipehead.org>; from paulkf@microgate.com on Tue, Oct 19, 2004 at 09:46:06PM -0500

On Tue, Oct 19, 2004 at 09:46:06PM -0500, Paul Fulghum wrote:
> On Tue, 2004-10-19 at 20:51, Steven E. Woolard wrote:
> > I ran into this problem when trying to compile 2.6.9-bk3 (since it came 
> > out less than 24 hours after 2.6.9 ... bad omen eh?)
> > I've attached my .config used just incase it helps. (New to bug 
> > reporting...)
> > ...
> >    CC      drivers/serial/8250.o
> > drivers/serial/8250.c:185: error: `UART_FCR_R_TRIG_10' undeclared here 
> > (not in a function)
> 
> Russell's patch introduces the use of
> the UART_FCR_x_TRIG_xx macros, but not
> the definition.

And the fix has been posted on this very mailing list shortly after the
problem code was merged:

  Subject: [PATCH] Fix serial breakage in -bk3
  Date:   Tue, 19 Oct 2004 23:47:16 +0100
  Message-ID: <20041019234716.D20243@flint.arm.linux.org.uk>


-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

      reply	other threads:[~2004-10-20  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20  1:51 Bug?: 2.6.9-bk3 Steven E. Woolard
2004-10-20  2:46 ` Paul Fulghum
2004-10-20  7:59   ` Russell King [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=20041020085918.B1047@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=paulkf@microgate.com \
    --cc=tuxq@tuxq.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 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.