From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
nuclearcat <nuclearcat@nuclearcat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pty_chars_in_buffer NULL pointer (kernel oops)
Date: Sat, 26 Feb 2005 11:18:58 +0000 [thread overview]
Message-ID: <1109415228.2584.0.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0502251935420.9237@ppc970.osdl.org>
I couldnt duplicate the performance hit so I believe the proper fix not
the hack is the right one
next prev parent reply other threads:[~2005-03-01 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 8:56 pty_chars_in_buffer NULL pointer (kernel oops) nuclearcat
2005-02-25 23:04 ` Marcelo Tosatti
2005-02-26 3:42 ` Linus Torvalds
2005-02-26 11:18 ` Alan Cox [this message]
2005-02-27 14:52 ` Re[2]: " nuclearcat
2005-02-27 15:03 ` Re[3]: " nuclearcat
-- strict thread matches above, loose matches on Subject: below --
2005-02-27 10:00 Marcelo Tosatti
2005-02-27 19:46 ` Linus Torvalds
2005-04-13 18:43 ` Jason Baron
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=1109415228.2584.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nuclearcat@nuclearcat.com \
--cc=torvalds@osdl.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