public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	Patrick Rudolph <patrick.rudolph@9elements.com>,
	Marcello Sylvester Bauer <sylv@sylv.io>
Subject: Re: [PATCH v2 3/5] regulator: max597x: Add support for max597x regulator
Date: Thu, 7 Jul 2022 14:43:48 +0100	[thread overview]
Message-ID: <YsbjFKyoSc2UxnBl@sirena.org.uk> (raw)
In-Reply-To: <20220707134141.1172300-4-Naresh.Solanki@9elements.com>

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

On Thu, Jul 07, 2022 at 03:41:39PM +0200, Naresh Solanki wrote:
> From: Patrick Rudolph <patrick.rudolph@9elements.com>
> 
> max597x is hot swap controller.
> This regulator driver controls the same & also configures fault
> protection features supported by the chip.

Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code.  Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.

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

  reply	other threads:[~2022-07-07 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:41 [PATCH v2 0/5] mfd: max597x: Add support for max597x Naresh Solanki
2022-07-07 13:41 ` [PATCH v2 1/5] dt-bindings: mfd: Add bindings for MAX5970 and MAX5978 Naresh Solanki
2022-07-07 13:41 ` [PATCH v2 2/5] mfd: max597x: Add support " Naresh Solanki
2022-08-08 13:55   ` Lee Jones
2022-07-07 13:41 ` [PATCH v2 3/5] regulator: max597x: Add support for max597x regulator Naresh Solanki
2022-07-07 13:43   ` Mark Brown [this message]
2022-07-07 13:41 ` [PATCH v2 4/5] iio: max597x: Add support for max597x Naresh Solanki
2022-07-07 14:38   ` kernel test robot
2022-07-07 13:41 ` [PATCH v2 5/5] leds: " Naresh Solanki

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=YsbjFKyoSc2UxnBl@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naresh.solanki@9elements.com \
    --cc=patrick.rudolph@9elements.com \
    --cc=sylv@sylv.io \
    /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