linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: "Kyungmin Park" <kmpark@infradead.org>,
	양진성 <jsgood.yang@samsung.com>,
	linux-input@vger.kernel.org, ben-linux@fluff.org,
	김경일/AP개발팀/E3/삼성전자 <ki0351.kim@samsung.com>,
	김국진/AP개발팀/E5/삼성전자 <kgene.kim@samsung.com>
Subject: Re: Fragmentation of Samsung SoC code (was INPUT][KEYBOARD] Add new keypad driver for s3c series SoCs)
Date: Mon, 7 Dec 2009 20:24:28 -0800	[thread overview]
Message-ID: <20091208042428.GE11147@core.coreip.homeip.net> (raw)
In-Reply-To: <20091020013914.GE24370@core.coreip.homeip.net>

Hi,

On Mon, Oct 19, 2009 at 06:39:14PM -0700, Dmitry Torokhov wrote:
> Ressurecting oldish topic...
> 
> On Mon, Sep 07, 2009 at 06:38:40PM +0900, Harald Welte wrote:
> > Hi Kyungmin,
> > 
> > On Mon, Sep 07, 2009 at 05:32:08PM +0900, Kyungmin Park wrote:
> > > 
> > > I think no problem to send several patch or drivers parallel. If so we
> > > can get more feedbacks.
> > 
> > I disagree.  Two departments of Samsung writing two drivers and then submitting
> > them to the mailinglists
> > 
> > 1) makes everyone, esp. the maintainer have to review two drivers
> > 2) confuses the maintainer, as he does not know which one to apply
> > 
> 
> So me being that confused maintainer having to chose between the 2
> drivers is wondering if you guys worked out which driver (if any) should
> go first and if there is an updated version that I need to review and
> apply...
> 

Now that the S3 touchscreen is on the way to Linus (will be in the next
pull request) did you guys get a chance to settle on keybiard driver by
any chance?

-- 
Dmitry

  reply	other threads:[~2009-12-08  4:24 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 [this message]
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
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=20091208042428.GE11147@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=jsgood.yang@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=ki0351.kim@samsung.com \
    --cc=kmpark@infradead.org \
    --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).