All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Christian Kohlschütter" <christian@kohlschutter.com>
Cc: m.szyprowski@samsung.com, heiko@sntech.de, lgirdwood@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-rockchip@lists.infradead.org, m.reichl@fivetechno.de,
	robin.murphy@arm.com, vincent.legoll@gmail.com, wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Mon, 29 Aug 2022 16:43:40 +0100	[thread overview]
Message-ID: <YwzerCnjvTKsEyIi@sirena.org.uk> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>

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

On Thu, Aug 25, 2022 at 09:28:42PM +0000, Christian Kohlschütter wrote:
> Previously, an unresolved regulator supply reference upon calling
> regulator_register on an always-on or boot-on regulator caused
> set_machine_constraints to be called twice.

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.

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

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

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: "Christian Kohlschütter" <christian@kohlschutter.com>
Cc: m.szyprowski@samsung.com, heiko@sntech.de, lgirdwood@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-rockchip@lists.infradead.org, m.reichl@fivetechno.de,
	robin.murphy@arm.com, vincent.legoll@gmail.com, wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Mon, 29 Aug 2022 16:43:40 +0100	[thread overview]
Message-ID: <YwzerCnjvTKsEyIi@sirena.org.uk> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>


[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]

On Thu, Aug 25, 2022 at 09:28:42PM +0000, Christian Kohlschütter wrote:
> Previously, an unresolved regulator supply reference upon calling
> regulator_register on an always-on or boot-on regulator caused
> set_machine_constraints to be called twice.

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.

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

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

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: "Christian Kohlschütter" <christian@kohlschutter.com>
Cc: m.szyprowski@samsung.com, heiko@sntech.de, lgirdwood@gmail.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-rockchip@lists.infradead.org, m.reichl@fivetechno.de,
	robin.murphy@arm.com, vincent.legoll@gmail.com, wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Mon, 29 Aug 2022 16:43:40 +0100	[thread overview]
Message-ID: <YwzerCnjvTKsEyIi@sirena.org.uk> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>


[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]

On Thu, Aug 25, 2022 at 09:28:42PM +0000, Christian Kohlschütter wrote:
> Previously, an unresolved regulator supply reference upon calling
> regulator_register on an always-on or boot-on regulator caused
> set_machine_constraints to be called twice.

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.

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-08-29 15:43 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 14:33 [PATCH v2] regulator: core: Resolve supply name earlier to prevent double-init Vincent Legoll
2022-08-04 10:44 ` [PATCH v3] " Christian Kohlschütter
2022-08-04 10:44   ` Christian Kohlschütter
2022-08-04 10:44   ` Christian Kohlschütter
2022-08-15 11:17   ` Mark Brown
2022-08-15 11:17     ` Mark Brown
2022-08-15 11:17     ` Mark Brown
2022-08-18 12:46     ` [PATCH v4] " Christian Kohlschütter
2022-08-18 12:46       ` Christian Kohlschütter
2022-08-18 12:46       ` Christian Kohlschütter
2022-08-18 15:23       ` Mark Brown
2022-08-18 15:23         ` Mark Brown
     [not found]       ` <CGME20220825113251eucas1p247c3d57de823da148ca4790975a4aba8@eucas1p2.samsung.com>
2022-08-25 11:32         ` Marek Szyprowski
2022-08-25 11:32           ` Marek Szyprowski
2022-08-25 11:32           ` Marek Szyprowski
2022-08-25 12:21           ` Mark Brown
2022-08-25 12:21             ` Mark Brown
2022-08-25 12:21             ` Mark Brown
2022-08-25 14:23             ` Marek Szyprowski
2022-08-25 14:23               ` Marek Szyprowski
2022-08-25 14:23               ` Marek Szyprowski
2022-08-25 15:18               ` Christian Kohlschütter
2022-08-25 15:18                 ` Christian Kohlschütter
2022-08-25 15:18                 ` Christian Kohlschütter
2022-08-25 21:28                 ` [PATCH v5] " Christian Kohlschütter
2022-08-25 21:28                   ` Christian Kohlschütter
2022-08-25 21:28                   ` Christian Kohlschütter
2022-08-25 21:35                   ` Christian Kohlschütter
2022-08-25 21:35                     ` Christian Kohlschütter
2022-08-25 21:35                     ` Christian Kohlschütter
2022-08-26  5:55                   ` Marek Szyprowski
2022-08-26  5:55                     ` Marek Szyprowski
2022-08-26  5:55                     ` Marek Szyprowski
2022-08-29 15:43                   ` Mark Brown [this message]
2022-08-29 15:43                     ` Mark Brown
2022-08-29 15:43                     ` Mark Brown
2022-08-29 17:01                     ` Christian Kohlschütter
2022-08-29 17:01                       ` Christian Kohlschütter
2022-08-29 17:01                       ` Christian Kohlschütter
2023-02-17 23:22                   ` Saravana Kannan
2023-02-17 23:22                     ` Saravana Kannan
2023-02-17 23:22                     ` Saravana Kannan
2023-02-17 23:33                     ` Christian Kohlschütter
2023-02-17 23:33                       ` Christian Kohlschütter
2023-02-17 23:33                       ` Christian Kohlschütter
2023-02-17 23:46                       ` Saravana Kannan
2023-02-17 23:46                         ` Saravana Kannan
2023-02-17 23:46                         ` Saravana Kannan
2023-02-18  0:01                         ` Christian Kohlschütter
2023-02-18  0:01                           ` Christian Kohlschütter
2023-02-18  0:01                           ` Christian Kohlschütter
2023-02-18  0:05                           ` Saravana Kannan
2023-02-18  0:05                             ` Saravana Kannan
2023-02-18  0:05                             ` Saravana Kannan
2022-08-18 15:22   ` [PATCH v3] " Mark Brown
2022-08-18 15:22     ` 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=YwzerCnjvTKsEyIi@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=christian@kohlschutter.com \
    --cc=heiko@sntech.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=m.reichl@fivetechno.de \
    --cc=m.szyprowski@samsung.com \
    --cc=robin.murphy@arm.com \
    --cc=vincent.legoll@gmail.com \
    --cc=wens@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.