mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrei Warkentin <awarkentin@vmware.com>
To: linux-kernel@vger.kernel.org
Cc: jason wessel <jason.wessel@windriver.com>,
	kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH] KDB: Fix usability issues relating to the 'enter' key.
Date: Fri, 24 Feb 2012 19:20:56 -0800 (PST)	[thread overview]
Message-ID: <1307333479.1554115.1330140056092.JavaMail.root@zimbra-prod-mbox-2.vmware.com> (raw)
In-Reply-To: <1329522773-21359-1-git-send-email-andreiw@vmware.com>

Hi,

----- Original Message -----
> From: "Andrei Warkentin" <andreiw@vmware.com>
> To: kgdb-bugreport@lists.sourceforge.net
> Cc: linux-kernel@vger.kernel.org, "jason wessel" <jason.wessel@windriver.com>, andreiw@vmware.com
> Sent: Friday, February 17, 2012 6:52:53 PM
> Subject: [PATCH] KDB: Fix usability issues relating to the 'enter' key.
> 
> This fixes the following problems:
> 1) Typematic-repeat of 'enter' gives warning message.
> 2) Use of 'keypad enter' gives warning message.
> 3) Lag on the order of seconds between "break" and "make" when
>    expecting the enter "break" code. Seen under virtualized
>    environments such as VMware ESX.
> 

Does this seem reasonable :-)?

A

  reply	other threads:[~2012-02-25  3:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 23:52 Andrei Warkentin
2012-02-25  3:20 ` Andrei Warkentin [this message]
2012-02-26 13:10 ` Jason Wessel
2012-02-26 13:58   ` Jason Wessel
2012-02-27  1:04     ` Andrei Warkentin
2012-02-27 22:50       ` Jason Wessel
2012-02-27 23:18         ` Andrei Warkentin
2012-02-27 23:28           ` Jason Wessel
2012-02-27 23:35             ` Andrei Warkentin
2012-02-28  1:27             ` Andrei Warkentin
2012-02-28  4:26             ` Andrei Warkentin
2012-02-28 13:53               ` Jason Wessel
2012-02-28 17:24                 ` Andrei Warkentin
2012-02-27  1:01   ` Andrei Warkentin

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=1307333479.1554115.1330140056092.JavaMail.root@zimbra-prod-mbox-2.vmware.com \
    --to=awarkentin@vmware.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --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

Powered by JetHome