public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	alan@linux.intel.com, stable@kernel.org,
	stable-commits@vger.kernel.org,
	"\"Frédéric L. W. Meunier\"" <fredlwm@gmail.com>,
	linux-kernel@vger.kernel.org, Boyan <btanastasov@yahoo.co.uk>
Subject: Re: patch pty-quickfix-for-the-pty-enxio-timing-problems.patch added to 2.6.31-stable tree
Date: Sat, 17 Oct 2009 17:35:56 +0200	[thread overview]
Message-ID: <4AD9E45C.2080807@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.01.0910151502020.6146@localhost.localdomain>

Linus Torvalds wrote:
> 
> On Thu, 15 Oct 2009, Greg KH wrote:
>> Hm, ok, Marcin asked that I include this patch as it fixed his keyboard
>> problems with X on 2.6.31.
>>
>> Marcin, any ideas?
> 
> Get current -git, I think it shoul be fixed there properly.
> 
> Marking the pty's "low_latency" works around the problem, but will break 
> at least ppp.
> 
> 		Linus

Greg, I see you queued c8e33141911bf8fe87dc6c92793b9a59b2be0130
(tty: Make flush_to_ldisc() locking more robust) for stable, so I guess
you figured out it was not my problems with keyboard (*), but Boyan's
and Frédéric's.

* http://lkml.org/lkml/2009/10/12/465

Marcin


      reply	other threads:[~2009-10-17 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091015184454.5BEDB48B35@coco.kroah.org>
     [not found] ` <alpine.LFD.2.01.0910151450420.6146@localhost.localdomain>
2009-10-15 21:54   ` patch pty-quickfix-for-the-pty-enxio-timing-problems.patch added to 2.6.31-stable tree Greg KH
2009-10-15 22:02     ` Linus Torvalds
2009-10-17 15:35       ` Marcin Slusarz [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=4AD9E45C.2080807@gmail.com \
    --to=marcin.slusarz@gmail.com \
    --cc=alan@linux.intel.com \
    --cc=btanastasov@yahoo.co.uk \
    --cc=fredlwm@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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