From: Lee Jones <lee.jones@linaro.org>
To: Florian Lobmaier <Florian.Lobmaier@ams.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: mfd: as3722: introducing ams AS3722 PMIC driver
Date: Tue, 20 Aug 2013 14:01:34 +0100 [thread overview]
Message-ID: <20130820130134.GP23699@lee--X1> (raw)
In-Reply-To: <EB31996D403C2C48A47628A08DCCFD2901857BCEF5@SUX2182.office.amsiag.com>
On Tue, 20 Aug 2013, Florian Lobmaier wrote:
> On Tue, 20 Aug 2013, Lee Jones wrote:
> > - http://kparal.wordpress.com/2011/08/18/git-tip-of-the-day-splitting-changes-into-several-patches/
>
> > - http://nuclearsquid.com/writings/git-add/
>
> Thank you very much for your hints and clarification on how to split up the patches. I think this point is clear to me now. We will need of course some time to split up the patches as requested.
No problem. Take as much time as you need.
> In addition, how to deal with the sub-drivers of the mfd? Should those be included in the mfd driver patch as they are introduced or should they be treated as separate units?
As long as each commit can be built as it's added and the pieces are
kept reasonably small, it doesn't matter too much. In an ideal world
each patch will only pertain to a single file, but sometimes adding
something in one file doesn't make any sense without the addition of
corresponding code in a related driver.
Just try to keep them separate with regards to subsystems, or else
matter will be complicated somewhat.
> Thanks again for your help, but as you might have already recognized, we are kernel newbies. At least in terms of getting code upstream.
That's fine. Everyone has to start from somewhere.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2013-08-20 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 11:13 mfd: as3722: introducing ams AS3722 PMIC driver Florian Lobmaier
2013-08-20 11:13 ` [PATCH 1/4] mfd: as3722: driver introduction in Kconfig and Makefile Florian Lobmaier
2013-08-20 11:59 ` Lee Jones
2013-08-20 11:13 ` [PATCH 2/4] mfd: as3722: introduce core driver file Florian Lobmaier
2013-08-20 12:03 ` Lee Jones
2013-08-20 11:13 ` [PATCH 3/4] mfd: as3722: introduce platform and register include files Florian Lobmaier
2013-08-20 12:05 ` Lee Jones
2013-08-20 11:13 ` [PATCH 4/4] mfd: as3722: introduce regmap support Florian Lobmaier
2013-08-20 12:08 ` Lee Jones
2013-08-21 18:28 ` Mark Brown
2013-08-22 9:25 ` Lee Jones
2013-08-21 18:30 ` Mark Brown
2013-08-20 11:56 ` mfd: as3722: introducing ams AS3722 PMIC driver Lee Jones
2013-08-20 12:32 ` Lee Jones
2013-08-20 12:39 ` Florian Lobmaier
2013-08-20 13:01 ` Lee Jones [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=20130820130134.GP23699@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