linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
Cc: sfr@canb.auug.org.au, Arnd Bergmann <arnd@arndb.de>,
	gregkh@suse.de, jbarnes@virtuousgeek.org, rubini@cvml.unipv.it,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fbdev@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Request for unicore32 architecture codes to merge into linux-next
Date: Sat, 15 Jan 2011 22:08:09 +0000	[thread overview]
Message-ID: <20110115220809.GC19872@core.coreip.homeip.net> (raw)
In-Reply-To: <004901cbb4d5$b9bb1370$2d313a50$@mprc.pku.edu.cn>

Hi,

On Sun, Jan 16, 2011 at 01:00:31AM +0800, Guan Xuetao wrote:
> Hi,
> 
> I want to merge unicore32 repo into linux-next tree, the position is (unicore32 branch):
>   git://git.kernel.org/pub/scm/linux/kernel/git/epip/linux-2.6-unicore32.git
> 

Have these changes been reviewed at all? Looking at the input parts I
doubt it... We try _really_ hard to avoid sprinkling arch #ifedefs in
the common code.

So, for input:

- how big is the difference between standard keytable and the one you
  are introducing? Looks like you are just adding 5 new keys that are
  not critical for booting. So please just update keymap from userpsace
  as we do for countless laptops and keyboards out there.

- Trying to enable mouse 1000 times can lead to loooong delays. Have
  you tried to figure out why you need the loop?

- What kind of mice can be connected to teh devices? I am concerned that
  your super-strict protocol checks will cause more harm then good (i do
  not believe they are valied in general case, overflow is just and
  additional bit).

Please split changes related into logically separated patches and post
them on linux-input@vger.kernel.org (along with linux-kernel if you
prefer) for review and comments.

Thanks.

-- 
Dmitry

  reply	other threads:[~2011-01-15 22:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 17:00 Request for unicore32 architecture codes to merge into linux-next Guan Xuetao
2011-01-15 22:08 ` Dmitry Torokhov [this message]
2011-01-16 15:35   ` Guan Xuetao
2011-01-18  4:33 ` Paul Mundt
2011-01-18  9:07   ` Guan Xuetao
2011-01-18  9:10     ` Paul Mundt
2011-01-18  9:33       ` Guan Xuetao
2011-01-18  9:53         ` Paul Mundt
2011-01-18 18:33 ` Request for unicore32 architecture codes to merge into Konrad Rzeszutek Wilk
2011-01-19  2:20   ` Request for unicore32 architecture codes to merge into linux-next Guan Xuetao
2011-01-20 19:42 ` Request for unicore32 architecture codes to merge into Jesse Barnes
2011-01-22  2:17   ` Request for unicore32 architecture codes to merge into linux-next Guan Xuetao

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=20110115220809.GC19872@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@suse.de \
    --cc=guanxuetao@mprc.pku.edu.cn \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rubini@cvml.unipv.it \
    --cc=sfr@canb.auug.org.au \
    /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).