linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jinsung Yang <jsgood.yang@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, ben-linux@fluff.org
Cc: linux-input@vger.kernel.org, laforge@gnumonks.org,
	"'김경일/AP개발팀(SYS.LSI)/E3(사원)/삼성전자'" <ki0351.kim@samsung.com>,
	"'김국진/AP개발팀(SYS.LSI)/E5(책임)/삼성전자'" <kgene.kim@samsung.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Fixed keypad driver for Samsung SoC
Date: Wed, 09 Sep 2009 20:13:14 +0900	[thread overview]
Message-ID: <000d01ca313e$867e7bd0$937b7370$%yang@samsung.com> (raw)

From: Jinsung Yang <jsgood.yang@samsung.com>

To Dmitry:
This patch series are including new Samsung SoC keypad driver with fixing wrong implementations which commented by you.
All changes and adds are in single patch.

[PATCH 1/4] [INPUT][KEYBOARD] Samsung keypad driver support

This patch depends on following architecture patches:

[PATCH 2/4] [ARM][S3C] Add definition for keypad platform data
[PATCH 3/4] [ARM][S3C] Add definition for keypad register
[PATCH 4/4] [ARM][S3C] Add support keypad platform data

To Ben:
As you know, I sent to you 12 patches for keypad driver some days ago,
however I need to change several patch files with following guidance:

This [PATCH 2/4] must be used instead of old [PATCH 07/12]
This [PATCH 3/4] must be used instead of old [PATCH 09/12]
This [PATCH 4/4] must be used instead of old both [PATCH 11/12] and [PATCH 12/12]

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




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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 11:13 Jinsung Yang [this message]
2009-09-09 11:27 ` [PATCH 0/4] Fixed keypad driver for Samsung SoC Jinsung Yang

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='000d01ca313e$867e7bd0$937b7370$%yang@samsung.com' \
    --to=jsgood.yang@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=ki0351.kim@samsung.com \
    --cc=laforge@gnumonks.org \
    --cc=linux-arm-kernel@lists.infradead.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).