From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/8] mfd: wm97xx-core: core support for wm97xx Codec
Date: Wed, 20 Sep 2017 12:34:46 +0100 [thread overview]
Message-ID: <20170920113446.ttwv23riutpp7e5i@sirena.org.uk> (raw)
In-Reply-To: <20170920082443.cqimrbhddum23lof@dell>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Wed, Sep 20, 2017 at 09:24:43AM +0100, Lee Jones wrote:
> On Tue, 19 Sep 2017, Mark Brown wrote:
> > It really helps if we can get the earlier parts of the series moving
> > even if the rest of it's in review still - I know I back off on
> > reviewing things if it looks like their dependencies aren't making
> > progress.
> Just for your FYI, I tend to review my parts then wait for the
> rest of the series to be reviewed, then discuss how the set should be
> handled.
> Holding back on reviewing your parts is not a good idea. If everyone
> did that we'd end up in a circular Maintainer dependency and nothing
> would ever get reviewed.
I get fed up with having to re-review the same patches over and over and
over again while people work out what's going on with the earlier parts
of the series, that gets very time consuming and is error prone. If
we're getting churn early on in the series that's causing things to
change then it's better to let that settle down and look properly at the
results than glaze over looking at each minor change as it comes in and
miss other things that get tweaked. Once the dependencies are stable
then it becomes worthwhile again.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-09-20 11:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 19:37 [PATCH v7 0/8] AC97 device/driver model revamp Robert Jarzmik
2017-09-13 19:37 ` [PATCH v7 1/8] Input: wm97xx: split out touchscreen registering Robert Jarzmik
2017-09-13 19:37 ` [PATCH v7 2/8] mfd: wm97xx-core: core support for wm97xx Codec Robert Jarzmik
2017-09-14 7:41 ` Lee Jones
2017-09-14 7:43 ` Lee Jones
2017-09-14 16:04 ` Mark Brown
2017-09-18 8:52 ` Lee Jones
2017-09-19 12:15 ` Mark Brown
2017-09-19 15:22 ` Lee Jones
2017-09-19 15:23 ` Lee Jones
2017-09-19 16:04 ` Mark Brown
2017-09-20 8:24 ` Lee Jones
2017-09-20 11:34 ` Mark Brown [this message]
2017-09-19 16:08 ` Mark Brown
2017-09-19 16:11 ` Applied "mfd: wm97xx-core: core support for wm97xx Codec" to the asoc tree Mark Brown
2017-09-13 19:37 ` [PATCH v7 3/8] Input: wm97xx: add new AC97 bus support Robert Jarzmik
2017-09-13 19:37 ` [PATCH v7 4/8] ASoC: wm9713: add ac97 new " Robert Jarzmik
2017-09-13 19:37 ` [PATCH v7 5/8] ASoC: wm9712: " Robert Jarzmik
2017-09-19 16:11 ` Applied "ASoC: wm9712: add ac97 new bus support" to the asoc tree Mark Brown
2017-09-13 19:37 ` [PATCH v7 6/8] ASoC: wm9705: add private structure Robert Jarzmik
2017-09-13 19:37 ` [PATCH v7 7/8] ASoC: wm9705: add ac97 new bus support Robert Jarzmik
2017-09-19 16:11 ` Applied "ASoC: wm9705: add ac97 new bus support" to the asoc tree Mark Brown
2017-09-13 19:37 ` [PATCH v7 8/8] ASoC: pxa: switch to new ac97 bus support Robert Jarzmik
2017-09-19 16:10 ` Mark Brown
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=20170920113446.ttwv23riutpp7e5i@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=daniel@zonque.org \
--cc=dmitry.torokhov@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=robert.jarzmik@free.fr \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®