mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linas@backlot.linas.org (Linas Vepstas)
To: Gunther.Mayer@t-online.de
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: resending-- Re: mouse problems in 2.4.2 -> lost byte -> Patch(2.4.3)!]
Date: Tue, 17 Apr 2001 17:44:07 -0500	[thread overview]
Message-ID: <20010417174407.L6403@backlot.linas.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

resending another lost message

----- Forwarded message from Linas Vepstas <linas@linas.org>, linas@linas.org -----

Subject: Re: mouse problems in 2.4.2 -> lost byte -> Patch(2.4.3)!
In-Reply-To: <3AD0C8AD.1A4D7D12@t-online.de> "from Gunther Mayer at Apr 8, 2001
	10:23:09 pm"
To: Gunther Mayer <Gunther.Mayer@t-online.de>
Date: Mon, 9 Apr 2001 18:42:51 -0500 (CDT)
From: Linas Vepstas <linas@linas.org>
CC: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk, 
	Vojtech Pavlik <vojtech@suse.cz>, linas@linas.org
X-Mailer: ELM [version 2.4ME+ PL87 (25)]

It's been rumoured that Gunther Mayer said:
> Losing bytes on psaux is a bug!
 [...]
> This patch printk's necessary information on the first 2 cases and

I had applied a similar set of printk's several weeks ago; however, 
now the problem refuses to recur.  Hmmm ... the last time I had a
problem that went away when I added printf's  ...

Just to be sure, I'm going to try running the kernel without the
printk's again.   Unfortunately, I upgraded the xserver yesterday,
and so I fear that may mask further re-occurances ...

--linas


----- End forwarded message -----

-- 
Linas Vepstas   -- linas@linas.org -- http://linas.org/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

                 reply	other threads:[~2001-04-17 22:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010417174407.L6403@backlot.linas.org \
    --to=linas@backlot.linas.org \
    --cc=Gunther.Mayer@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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

all inboxes | Powered by JetHome®