From: Mark Brown <broonie@kernel.org>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-gpio@ger.kernel.org" <linux-gpio@ger.kernel.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Subject: Re: [PATCH v13 00/11] Support ROHM BD71828 PMIC
Date: Tue, 21 Jan 2020 13:11:00 +0000 [thread overview]
Message-ID: <20200121131100.GB4656@sirena.org.uk> (raw)
In-Reply-To: <70ac7b71d5d54d4b90ded032214c473569b9fae1.camel@fi.rohmeurope.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Mon, Jan 20, 2020 at 02:21:09PM +0000, Vaittinen, Matti wrote:
> On Mon, 2020-01-20 at 13:54 +0000, Mark Brown wrote:
> > stop sending me this series until the MFD has been merged, perhaps
> > just
> > drop the subsystem patches while you resolve whatever the problems
> > are
> > that remain with the MFD? I'm pretty much just deleting these
> I was hoping the revision history in cover letter would be a fast way
> to determine if something relevant has changed. Additionally, I did try
All I'm looking at mostly is to see if my Acked-by tag went away due to
changes, I might look at the rest of a series if I have time but if I've
checked the bit that's relevant to me I'm not going to worry too much
about the rest of it.
> But sure, I should try to be more careful so that I don't need to do so
> many resends - and I really could drop most of the recipients earlier.
> Thanks for pointing it out.
What I was suggesting was more just dropping the driver bits while the
MFD gets resolved, I'm never 100% sure why but the core MFD often takes
a long time to figure out as seems to be the case here. There might be
as many individual resends overall but each maintainer will see fewer of
them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-21 13:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 13:40 [PATCH v13 00/11] Support ROHM BD71828 PMIC Matti Vaittinen
2020-01-20 13:40 ` [PATCH v13 01/11] dt-bindings: leds: ROHM BD71282 PMIC LED driver Matti Vaittinen
2020-01-20 13:41 ` [PATCH v13 02/11] dt-bindings: mfd: Document ROHM BD71828 bindings Matti Vaittinen
2020-01-20 13:42 ` [PATCH v13 03/11] mfd: rohm PMICs - use platform_device_id to match MFD sub-devices Matti Vaittinen
2020-01-21 16:40 ` Mark Brown
2020-01-22 6:15 ` Vaittinen, Matti
2020-01-20 13:43 ` [PATCH v13 04/11] mfd: bd718x7: Add compatible for BD71850 Matti Vaittinen
2020-01-20 13:43 ` [PATCH v13 05/11] mfd: bd71828: Support ROHM BD71828 PMIC - core Matti Vaittinen
2020-01-20 13:43 ` [PATCH v13 06/11] mfd: bd71828: Add power-key support Matti Vaittinen
2020-01-20 13:44 ` [PATCH v13 07/11] clk: bd718x7: Support ROHM BD71828 clk block Matti Vaittinen
2020-01-20 13:44 ` [PATCH v13 08/11] regulator: bd718x7: Split driver to common and bd718x7 specific parts Matti Vaittinen
2020-01-20 13:45 ` [PATCH v13 09/11] mfd: bd70528: Fix hour register mask Matti Vaittinen
2020-01-20 13:45 ` [PATCH v13 10/11] rtc: bd70528: add BD71828 support Matti Vaittinen
2020-01-20 13:47 ` [PATCH v13 11/11] gpio: bd71828: Initial support for ROHM BD71828 PMIC GPIOs Matti Vaittinen
2020-01-20 13:54 ` [PATCH v13 00/11] Support ROHM BD71828 PMIC Mark Brown
2020-01-20 14:21 ` Vaittinen, Matti
2020-01-21 8:34 ` Lee Jones
2020-01-21 13:11 ` Mark Brown [this message]
2020-01-22 6:44 ` Vaittinen, Matti
2020-01-22 12:19 ` Mark Brown
2020-01-21 8:36 ` Lee Jones
2020-01-21 16:15 ` Mark Brown
2020-01-22 6:28 ` Vaittinen, Matti
2020-01-22 11:58 ` Mark Brown
2020-01-22 7:32 ` Lee Jones
2020-01-22 12:11 ` Mark Brown
2020-01-22 13:33 ` Lee Jones
2020-01-24 7:32 ` [GIT PULL] Immutable branch between MFD, Clk, GPIO, Regulator and RTC due for the v5.6 merge window 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=20200121131100.GB4656@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@ger.kernel.org \
--cc=mazziesaccount@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox