From: Lee Jones <lee.jones@linaro.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 0/7] drivers/mfd: make max drivers explicitly non-modular
Date: Mon, 4 Apr 2016 15:21:04 +0100 [thread overview]
Message-ID: <20160404142104.GW3323@x1> (raw)
In-Reply-To: <20160404135146.GF1778@windriver.com>
On Mon, 04 Apr 2016, Paul Gortmaker wrote:
> [Re: [PATCH 0/7] drivers/mfd: make max drivers explicitly non-modular] On 04/04/2016 (Mon 09:11) Lee Jones wrote:
>
> > How did you come up with the subject lines for these patches?
>
> I just used the general default of:
> <path_to_subsystem>: rest of subject
>
> >
> > Please do `git log --oneline -- <subsystem>`, as is normal when
> > submitting to mainline.
>
> Just to be clear, looking at other mfd history, you want me to just
> drop the "drivers/" prefix ; i.e. change from:
>
> drivers/mfd: text text text driver.c text
>
> ...to:
>
> mfd: text text text driver.c text
>
> If so, that is no problem and I can do that for the next revision when I
> drop the patches pending tristate conversion that I wasn't aware of.
Current subsystem format is:
mfd: sub-driver-name: Thing you're doing
Sub-driver-name doesn't require file extensions and 'Think that you're
doing" should start with an uppercase character.
(Royal-)We like straight lines and conformity. ;)
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-04-04 14:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 21:24 [PATCH 0/7] drivers/mfd: make max drivers explicitly non-modular Paul Gortmaker
2016-04-03 21:24 ` [PATCH 1/7] drivers/mfd: make max8925-i2c.c " Paul Gortmaker
2016-04-03 21:24 ` [PATCH 2/7] drivers/mfd: make max8997.c " Paul Gortmaker
2016-04-03 21:24 ` [PATCH 3/7] drivers/mfd: make max8998.c " Paul Gortmaker
2016-04-03 21:24 ` [PATCH 4/7] drivers/mfd: make max14577.c " Paul Gortmaker
2016-04-04 3:42 ` Krzysztof Kozlowski
2016-04-04 15:09 ` Paul Gortmaker
2016-04-05 14:24 ` Javier Martinez Canillas
2016-04-03 21:24 ` [PATCH 5/7] drivers/mfd: make max77686.c " Paul Gortmaker
2016-04-04 3:44 ` Krzysztof Kozlowski
2016-04-04 15:08 ` Paul Gortmaker
2016-04-04 15:21 ` Javier Martinez Canillas
2016-04-03 21:24 ` [PATCH 6/7] drivers/mfd: make max77693.c " Paul Gortmaker
2016-04-04 3:53 ` Krzysztof Kozlowski
2016-04-04 15:39 ` Paul Gortmaker
2016-04-05 2:06 ` Krzysztof Kozlowski
2016-04-03 21:24 ` [PATCH 7/7] drivers/mfd: make max77843.c " Paul Gortmaker
2016-04-04 8:11 ` [PATCH 0/7] drivers/mfd: make max drivers " Lee Jones
2016-04-04 13:51 ` Paul Gortmaker
2016-04-04 14:21 ` 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=20160404142104.GW3323@x1 \
--to=lee.jones@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=haojian.zhuang@marvell.com \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=paul.gortmaker@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.