All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Kohlschütter" <christian@kohlschutter.com>
To: Mark Brown <broonie@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Linux MMC List" <linux-mmc@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"Markus Reichl" <m.reichl@fivetechno.de>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Vincent Legoll" <vincent.legoll@gmail.com>,
	wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Thu, 25 Aug 2022 23:35:27 +0200	[thread overview]
Message-ID: <395E54FA-15D2-48C7-A076-20E9B9398C22@kohlschutter.com> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>

This needed some further rearrangement. Please validate v5 of the patch.

Any branch that has the v4 patch should revert that change and freshly re-apply the v5 patch.
I hope this simplifies merging into mainline.

Verified by
1. rebooting numerous times (no mmc errors, partitions on mmc SD card are properly detected, no hangs upon reboot, i.e., the change appears to work)
2. "cat /sys/kernel/debug/regulator/regulator_summary" now correctly shows regulators, regulator-dummy use count is 1
3. ensuring that no entries for "(null)-SUPPLY' were found in dmesg or /sys

Thanks,
Christian


WARNING: multiple messages have this Message-ID (diff)
From: "Christian Kohlschütter" <christian@kohlschutter.com>
To: Mark Brown <broonie@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Linux MMC List" <linux-mmc@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"Markus Reichl" <m.reichl@fivetechno.de>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Vincent Legoll" <vincent.legoll@gmail.com>,
	wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Thu, 25 Aug 2022 23:35:27 +0200	[thread overview]
Message-ID: <395E54FA-15D2-48C7-A076-20E9B9398C22@kohlschutter.com> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>

This needed some further rearrangement. Please validate v5 of the patch.

Any branch that has the v4 patch should revert that change and freshly re-apply the v5 patch.
I hope this simplifies merging into mainline.

Verified by
1. rebooting numerous times (no mmc errors, partitions on mmc SD card are properly detected, no hangs upon reboot, i.e., the change appears to work)
2. "cat /sys/kernel/debug/regulator/regulator_summary" now correctly shows regulators, regulator-dummy use count is 1
3. ensuring that no entries for "(null)-SUPPLY' were found in dmesg or /sys

Thanks,
Christian


_______________________________________________
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: "Christian Kohlschütter" <christian@kohlschutter.com>
To: Mark Brown <broonie@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Linux MMC List" <linux-mmc@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"Markus Reichl" <m.reichl@fivetechno.de>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Vincent Legoll" <vincent.legoll@gmail.com>,
	wens@kernel.org
Subject: Re: [PATCH v5] regulator: core: Resolve supply name earlier to prevent double-init
Date: Thu, 25 Aug 2022 23:35:27 +0200	[thread overview]
Message-ID: <395E54FA-15D2-48C7-A076-20E9B9398C22@kohlschutter.com> (raw)
In-Reply-To: <20220825212842.7176-1-christian@kohlschutter.com>

This needed some further rearrangement. Please validate v5 of the patch.

Any branch that has the v4 patch should revert that change and freshly re-apply the v5 patch.
I hope this simplifies merging into mainline.

Verified by
1. rebooting numerous times (no mmc errors, partitions on mmc SD card are properly detected, no hangs upon reboot, i.e., the change appears to work)
2. "cat /sys/kernel/debug/regulator/regulator_summary" now correctly shows regulators, regulator-dummy use count is 1
3. ensuring that no entries for "(null)-SUPPLY' were found in dmesg or /sys

Thanks,
Christian


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

  reply	other threads:[~2022-08-25 21:35 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 [this message]
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
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=395E54FA-15D2-48C7-A076-20E9B9398C22@kohlschutter.com \
    --to=christian@kohlschutter.com \
    --cc=broonie@kernel.org \
    --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.