linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Philip Langdale <philipl@overt.org>,
	linux-input@vger.kernel.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: INPUT_COMPAT_TEST
Date: Sat, 09 Jul 2011 01:04:53 -0700	[thread overview]
Message-ID: <4E180BA5.4080808@zytor.com> (raw)
In-Reply-To: <20110709003508.GC28623@core.coreip.homeip.net>

On 07/08/2011 05:35 PM, Dmitry Torokhov wrote:
> 
> Input only need to do this compat stuff on read/write paths so maybe if
> you add plumbing similar to compat_ioctl we could switch owver to it.
> 

The problem is that read/write ties into a large number of system calls,
and input is the *only* subsystem which needs it.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2011-07-09  8:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 18:45 INPUT_COMPAT_TEST H. Peter Anvin
2011-07-08 20:46 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-08 22:22   ` INPUT_COMPAT_TEST H. Peter Anvin
2011-07-08 22:37     ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-08 22:44       ` INPUT_COMPAT_TEST Thadeu Lima de Souza Cascardo
2011-07-08 23:18       ` INPUT_COMPAT_TEST H. Peter Anvin
2011-07-09  0:35         ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-07-09  8:04           ` H. Peter Anvin [this message]
2011-09-07 18:16             ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-09-07 18:22               ` INPUT_COMPAT_TEST H. Peter Anvin
2011-09-07 18:37                 ` INPUT_COMPAT_TEST Dmitry Torokhov
2011-09-07 18:40                   ` INPUT_COMPAT_TEST H. Peter Anvin
2011-09-07 18:54                     ` INPUT_COMPAT_TEST Dmitry Torokhov

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=4E180BA5.4080808@zytor.com \
    --to=hpa@zytor.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=philipl@overt.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;
as well as URLs for NNTP newsgroup(s).