From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
robh+dt@kernel.org, mark.rutland@arm.com, lgirdwood@gmail.com,
sboyd@kernel.org, mazziesaccount@gmail.com,
heikki.haikola@fi.rohmeurope.com,
mikko.mutanen@fi.rohmeurope.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v3 1/7] regulator/mfd: Support ROHM BD71847 power management IC
Date: Mon, 8 Oct 2018 23:02:22 -0700 [thread overview]
Message-ID: <20181009060222.GA4324@dell> (raw)
In-Reply-To: <20180928133046.GL20825@sirena.org.uk>
On Fri, 28 Sep 2018, Mark Brown wrote:
> On Fri, Sep 28, 2018 at 10:14:37AM +0300, Matti Vaittinen wrote:
>
> > I was just wondering if I could do something to help get this patch
> > series applied? Mark, have you had the time to take a look on pickable
> > ranges addition yet? Should I do some rebasing/resending? Are you giving
> > me a nudge if I can do something?
>
> Please don't send content free pings and please allow a reasonable time
> for review. People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review. If there have been
> review comments then people may be waiting for those to be addressed.
> Sending content free pings just adds to the mail volume (if they are
> seen at all) and if something has gone wrong you'll have to resend the
> patches anyway so resending with any comments addressed is generally a
> much better approach.
Steeling and adding to an Emacs key-combo for easy insertion into mails!
--
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-10-09 6:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:27 [PATCH v3 0/7] regulator/mfd/dt_bindings: bd718x7: Support ROHM bd71847 Matti Vaittinen
2018-09-14 8:27 ` [PATCH v3 1/7] regulator/mfd: Support ROHM BD71847 power management IC Matti Vaittinen
2018-09-21 17:29 ` Mark Brown
2018-09-21 18:02 ` Lee Jones
2018-09-21 18:12 ` Mark Brown
2018-09-21 18:52 ` Lee Jones
2018-09-28 7:14 ` Matti Vaittinen
2018-09-28 13:30 ` Mark Brown
2018-10-09 6:02 ` Lee Jones [this message]
2018-09-28 14:01 ` Mark Brown
2018-09-14 8:30 ` [PATCH v3 2/7] regulator: dt bindings: add BD71847 device-tree binding documentation Matti Vaittinen
2018-09-14 8:30 ` [PATCH v3 3/7] mfd: " Matti Vaittinen
2018-09-14 8:31 ` [PATCH v3 4/7] regulator: Support regulators where voltage ranges are selectable Matti Vaittinen
2018-09-14 8:32 ` [PATCH v3 5/7] regulator/mfd: bd718xx: rename bd71837/bd71847 common instances Matti Vaittinen
2018-09-14 8:33 ` [PATCH v3 6/7] regulator: bd718XX use pickable ranges Matti Vaittinen
2018-09-14 8:34 ` [PATCH v3 7/7] regulator: bd718xx: rename bd71837 to 718xx Matti Vaittinen
2018-09-18 10:13 ` kbuild test robot
2018-09-18 10:13 ` kbuild test robot
2018-09-19 6:32 ` Matti Vaittinen
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=20181009060222.GA4324@dell \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heikki.haikola@fi.rohmeurope.com \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@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=robh+dt@kernel.org \
--cc=sboyd@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 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.