LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Mallikarjun Kasoju <mkasoju@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 6/6] regulator: max77620: Support Maxim 77663
Date: Sun, 12 May 2019 18:07:17 +0100	[thread overview]
Message-ID: <20190512170717.GS21483@sirena.org.uk> (raw)
In-Reply-To: <f8f67e00-0544-c999-92e0-3998c2f70ee7@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

On Sun, May 12, 2019 at 05:08:15PM +0300, Dmitry Osipenko wrote:

> Just want to get yours attention to that Lee picked up the patches into
> the MFD tree, excluding this patch. I assume this one will have to go
> via the regulator's tree.

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 adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-05-12 17:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 15:43 [PATCH v4 0/6] Add support for Maxim 77663 MFD Dmitry Osipenko
2019-05-05 15:43 ` [PATCH v4 1/6] dt-bindings: mfd: max77620: Add compatible for Maxim 77663 Dmitry Osipenko
2019-05-08 11:46   ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 2/6] dt-bindings: mfd: max77620: Add system-power-controller property Dmitry Osipenko
2019-05-07 17:46   ` Rob Herring
2019-05-08 11:46   ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 3/6] mfd: max77620: Fix swapped FPS_PERIOD_MAX_US values Dmitry Osipenko
2019-05-08 11:47   ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 4/6] mfd: max77620: Support Maxim 77663 Dmitry Osipenko
2019-05-08 11:47   ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 5/6] mfd: max77620: Provide system power-off functionality Dmitry Osipenko
2019-05-08 11:48   ` Lee Jones
2019-05-05 15:43 ` [PATCH v4 6/6] regulator: max77620: Support Maxim 77663 Dmitry Osipenko
2019-05-12 14:08   ` Dmitry Osipenko
2019-05-12 17:07     ` Mark Brown [this message]
2019-05-08 11:51 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v5.2 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=20190512170717.GS21483@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mkasoju@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --subject='Re: [PATCH v4 6/6] regulator: max77620: Support Maxim 77663' \
    /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

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).