public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Florian Lobmaier <florian.lobmaier@ams.com>
Cc: linux-kernel@vger.kernel.org, sameo@linux.intel.com
Subject: Re: [PATCH 4/4] added ams AS3722 register include file
Date: Wed, 14 Aug 2013 16:33:25 +0100	[thread overview]
Message-ID: <20130814153325.GG4046@lee--X1> (raw)
In-Reply-To: <1376492098-15672-4-git-send-email-florian.lobmaier@ams.com>

> ---
>  include/linux/mfd/as3722-reg.h |  495 ++++++++++++++++++++++++++++++++++++++++

So the way you've split up the patch isn't quite right. It shouldn't
be split by files, rather by functionality.

Quoting from Documentation/SubmittingPatches:

"If your changes produce a lot of deltas, you may want to look into
 splitting them into individual patches which modify things in
 logical stages.  This will facilitate easier reviewing by other
 kernel developers, very important if you want your patch accepted."

Note "logical stages".

So things like:

- Driver introduction including Kconfig and Makefile entries
- Resource allocation; memory and irqs
- Everything else, bit by bit

Within reason, the simpler the patches, they more likely they are to
be reviewed and accepted.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2013-08-14 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 14:54 [PATCH 1/4] added support for ams AS3722 PMIC in mfd Florian Lobmaier
2013-08-14 14:54 ` [PATCH 2/4] added regmap of AS3722 Florian Lobmaier
2013-08-14 15:29   ` Mark Brown
2013-08-14 14:54 ` [PATCH 3/4] added AS3722 platform include file Florian Lobmaier
2013-08-14 14:54 ` [PATCH 4/4] added ams AS3722 register " Florian Lobmaier
2013-08-14 15:33   ` Lee Jones [this message]
2013-08-14 15:27 ` [PATCH 1/4] added support for ams AS3722 PMIC in mfd Lee Jones
2013-08-14 15:27 ` Mark Brown

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=20130814153325.GG4046@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=florian.lobmaier@ams.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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