From: Russell King <rmk+lkml@arm.linux.org.uk>
To: John Stoffel <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.18-rc1-mm1 - bad serial port count messages
Date: Tue, 11 Jul 2006 21:15:21 +0100 [thread overview]
Message-ID: <20060711201521.GC3677@flint.arm.linux.org.uk> (raw)
In-Reply-To: <17588.997.688135.786150@stoffel.org>
On Tue, Jul 11, 2006 at 04:02:45PM -0400, John Stoffel wrote:
> I thought I saw something float by where someone had raised some new
> locking or count variables? I dunno... I'll work on it tonight and
> see what happens after another reboot.
Those are probably changes in the tty layer - Jon Smirl is attempting
some tty changes.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-07-11 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 13:20 2.6.18-rc1-mm1 - bad serial port count messages John Stoffel
2006-07-11 18:56 ` Russell King
2006-07-11 20:02 ` John Stoffel
2006-07-11 20:15 ` 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=20060711201521.GC3677@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=john@stoffel.org \
--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