From: Michael Schutte <michi@uiae.at>
To: linux-kernel@vger.kernel.org
Cc: Samuel Thibault <samuel.thibault@labri.fr>
Subject: Re: [PATCH] fs/compat_ioctl.c: Add KD[GS]KBDIACRUC to the compatible list
Date: Fri, 1 Jan 2010 18:59:36 +0100 [thread overview]
Message-ID: <20100101175936.GA2878@graeme> (raw)
In-Reply-To: <201001011820.51144.arnd@arndb.de>
On Fri, Jan 01, 2010 at 06:20:50PM +0100, Arnd Bergmann wrote:
> On Friday 01 January 2010, Michael Schutte wrote:
> > Allow handling of Unicode compose sequences by 32-bit apps on a 64-bit
> > system. The issue has been reported in <http://bugs.debian.org/540534>
> > and <http://lists.altlinux.org/pipermail/kbd/2009-December/000235.html>.
> > […]
>
> Since 2.6.32, we handle all VT specific ioctls in the vt_compat_ioctl()
> function, which should fix this one implicitly. Please try to reproduce
> with a recent kernel.
Works indeed. Thank you for the pointer and sorry for the noise.
Cheers,
--
Michael Schutte <michi@uiae.at>
prev parent reply other threads:[~2010-01-01 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 13:56 [PATCH] fs/compat_ioctl.c: Add KD[GS]KBDIACRUC to the compatible list Michael Schutte
2010-01-01 17:20 ` Arnd Bergmann
2010-01-01 17:59 ` Michael Schutte [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=20100101175936.GA2878@graeme \
--to=michi@uiae.at \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@labri.fr \
/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