linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jinsung Yang <jsgood.yang@samsung.com>
To: 'Joonyoung Shim' <jy0922.shim@samsung.com>,
	'Harald Welte' <laforge@gnumonks.org>
Cc: linux-input@vger.kernel.org, ben-linux@fluff.org,
	"'\"김경일/AP개발팀(SYS.LSI)/E3(사원)/삼성전자\"'" <ki0351.kim@samsung.com>,
	"'\"'김국진/AP개발팀(SYS.LSI)/E5(책임)/삼성전자'\"'" <kgene.kim@samsung.com>,
	dmitry.torokhov@gmail.com, kyungmin.park@samsung.com,
	jh80.chung@samsung.com
Subject: RE: [PATCH 03/03] [INPUT][KEYBOARD] Add new keypad driver for s3c series SoCs
Date: Mon, 07 Sep 2009 20:32:19 +0900	[thread overview]
Message-ID: <002c01ca2fae$dc327630$94976290$%yang@samsung.com> (raw)
In-Reply-To: <4AA4B6E9.2070603@samsung.com>

Hi, Mr.Shim

> >    submitted mainline.  This is what Jinsun was starting, and which he
> >    will continue until it is included mainline.
> >
> 
> The keypad of s3c64xx and s5pc1xx is same almost, so we need to submit
> the well-defined driver from the first.

I have some questions:
1) Could you explain to us what is the 'well-defined' driver?
2) Did you test your keypad driver at s3c6410 based platform?
3) There is no architecture codes for s5pc1xx series, why did you send keypad driver first for s5pc1xx before architecture codes?

Best Regards
--
Jinsung, Yang <jsgood.yang@samsung.com>
AP Development Team
System LSI, Semiconductor Business
SAMSUNG Electronics Co., LTD



  reply	other threads:[~2009-09-07 11:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 13:55 [PATCH 03/03] [INPUT][KEYBOARD] Add new keypad driver for s3c series SoCs 양진성
2009-09-05 16:17 ` Mark Brown
2009-09-07  3:25 ` Kyungmin Park
2009-09-07  3:50   ` Jinsung Yang
2009-09-07  6:26   ` Harald Welte
2009-09-07  6:59     ` Kyungmin Park
2009-09-07  8:02       ` Fragmentation of Samsung SoC code (was INPUT][KEYBOARD] Add new keypad driver for s3c series SoCs) Harald Welte
2009-09-07  8:32         ` Kyungmin Park
2009-09-07  9:38           ` Harald Welte
2009-10-20  1:39             ` Dmitry Torokhov
2009-12-08  4:24               ` Dmitry Torokhov
2009-12-08  4:52                 ` Jinsung Yang
2009-09-07  5:38 ` [PATCH 03/03] [INPUT][KEYBOARD] Add new keypad driver for s3c series SoCs Joonyoung Shim
2009-09-07  6:33   ` Harald Welte
2009-09-07  7:31     ` Joonyoung Shim
2009-09-07 11:32       ` Jinsung Yang [this message]
2009-09-07 12:15         ` Joonyoung Shim
2009-09-07 12:38           ` Jinsung Yang
2009-09-07 13:14             ` Kyungmin Park
2009-09-07 13:40               ` Kyungmin Park
2009-09-07 13:42             ` Joonyoung Shim
2009-09-07  7:48   ` Dmitry Torokhov
2009-09-07  8:40     ` Joonyoung Shim
2009-09-08  4:44       ` Dmitry Torokhov
2009-09-17  2:17         ` Joonyoung Shim
2009-09-07  8:00 ` 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='002c01ca2fae$dc327630$94976290$%yang@samsung.com' \
    --to=jsgood.yang@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=jy0922.shim@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=ki0351.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=laforge@gnumonks.org \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).