linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: 양진성 <jsgood.yang@samsung.com>
Cc: linux-input@vger.kernel.org, laforge@gnumonks.org,
	ben-linux@fluff.org,
	"김경일/AP개발팀(SYS.LSI)/E3(사원)/삼성전자" <ki0351.kim@samsung.com>,
	"'김국진/AP개발팀(SYS.LSI)/E5(책임)/삼성전자'" <kgene.kim@samsung.com>
Subject: Re: [PATCH 01/03] [INPUT][KEYBOARD] Kconfig support for s3c matrix keypad
Date: Sat, 5 Sep 2009 16:56:43 +0100	[thread overview]
Message-ID: <20090905155642.GA10326@sirena.org.uk> (raw)
In-Reply-To: <00b001ca2e30$6c79ccf0$456d66d0$%yang@samsung.com>

On Sat, Sep 05, 2009 at 10:54:44PM +0900, 양진성 wrote:
> This patch supports to select configuration for s3c matrix keypad.

> Signed-off-by: Jinsung Yang <jsgood.yang@samsung.com>
> Signed-off-by: Kyeongil Kim <ki0351.kim@samsung.com>

A relatively technical point but you should always try to order your
patch series so that the kernel always builds, even with the patch
series partly applied.  This means that if you've split out the build
system changes that should be the last patch in the series.

Doing this is useful when people use tools such as 'git bisect' which
walk through history and also means that it's possible to do things like
partially apply the series (for example, if you get a situation where
the earlier patches are all OK but there's some issues that need to be
resolved in the later ones).

It'd probably also help to combine more of your changes together - in
general it's better if patches achieve some goal in a self-contained
fashion.  This normally makes things easier to review.  Things like
doing the build system separately are normally there in order to split a
very large driver into managable chunks.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-09-05 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 13:54 [PATCH 01/03] [INPUT][KEYBOARD] Kconfig support for s3c matrix keypad 양진성
2009-09-05 15:56 ` Mark Brown [this message]

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=20090905155642.GA10326@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ben-linux@fluff.org \
    --cc=jsgood.yang@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=ki0351.kim@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).