From: Lee Jones <lee.jones@linaro.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, lgirdwood@gmail.com, broonie@kernel.org,
mazziesaccount@gmail.com, arnd@arndb.de,
dmitry.torokhov@gmail.com, sre@kernel.org, chenjh@rock-chips.com,
andrew.smirnov@gmail.com, linus.walleij@linaro.org,
kstewart@linuxfoundation.org, heiko@sntech.de,
gregkh@linuxfoundation.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com,
heikki.haikola@fi.rohmeurope.com
Subject: Re: [PATCH v7 0/4] mfd/regulator/clk/input: bd71837: ROHM BD71837 PMIC driver
Date: Tue, 3 Jul 2018 08:02:00 +0100 [thread overview]
Message-ID: <20180703070200.GC20176@dell> (raw)
In-Reply-To: <20180621103400.GB6076@localhost.localdomain>
On Thu, 21 Jun 2018, Matti Vaittinen wrote:
> On Tue, Jun 19, 2018 at 01:55:31PM +0300, Matti Vaittinen wrote:
> > Patch series adding support for ROHM BD71837 PMIC.
> >
> What is the preferred way when I send updated patches:
>
> 1. always resend _all_ unapplied patches even if there is no changes to
> some of them. (patch-vN mail thread contains _all_ unapplied patches)
> 2. only resend changed patches (patch-vN mail thread contains only
> patches that were changed from patch-vN-1)
>
> I have currently used approach 1 - so that no patches would be
> accidentally forgotten - but downside is that people need to check if
> they have already reviewed some of the patches. I'd rather not caused
> any extra work. What is the most convenient way for you guys?
Option 1 is preferred.
Just ensure you apply any tags you have collected so reviewers can see
which patches are pending a review. It's also a good idea to keep a
succinct change log between the "--" marker and the diff stat where
you can state "v4: No change" or the like.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-07-03 7:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 10:55 [PATCH v7 0/4] mfd/regulator/clk/input: bd71837: ROHM BD71837 PMIC driver Matti Vaittinen
2018-06-19 10:55 ` [PATCH v7 1/4] mfd: bd71837: mfd driver for ROHM BD71837 PMIC Matti Vaittinen
2018-06-26 9:06 ` Enric Balletbo Serra
2018-06-26 11:24 ` Matti Vaittinen
2018-06-26 11:40 ` Enric Balletbo Serra
2018-06-26 12:03 ` Matti Vaittinen
2018-06-26 14:24 ` Enric Balletbo Serra
2018-07-03 6:56 ` Lee Jones
2018-07-03 8:09 ` Enric Balletbo Serra
2018-07-03 6:53 ` Lee Jones
2018-07-04 14:56 ` Dmitry Torokhov
2018-07-04 16:57 ` Enric Balletbo Serra
2018-07-05 5:52 ` Lee Jones
2018-07-05 7:56 ` Matti Vaittinen
2018-07-06 6:38 ` Dmitry Torokhov
2018-07-06 7:05 ` Lee Jones
2018-07-06 7:49 ` Matti Vaittinen
2018-06-19 10:56 ` [PATCH v7 2/4] mfd: bd71837: Devicetree bindings " Matti Vaittinen
2018-06-19 10:56 ` [PATCH v7 3/4] clk: bd71837: Add driver for BD71837 PMIC clock Matti Vaittinen
2018-06-19 10:57 ` [PATCH v7 4/4] input/power: Add driver for BD71837/BD71847 PMIC power button Matti Vaittinen
2018-06-19 17:50 ` Dmitry Torokhov
2018-06-20 6:43 ` Matti Vaittinen
2018-06-21 10:25 ` Matti Vaittinen
2018-06-27 0:21 ` Dmitry Torokhov
2018-06-21 10:34 ` [PATCH v7 0/4] mfd/regulator/clk/input: bd71837: ROHM BD71837 PMIC driver Matti Vaittinen
2018-07-03 7:02 ` Lee Jones [this message]
2018-07-04 8:47 ` Matti Vaittinen
2018-07-04 9:21 ` Lee Jones
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=20180703070200.GC20176@dell \
--to=lee.jones@linaro.org \
--cc=andrew.smirnov@gmail.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=chenjh@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=heiko@sntech.de \
--cc=kstewart@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mikko.mutanen@fi.rohmeurope.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sre@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).