| Message ID | 20220119103747.58305-1-alexander.stein@ew.tq-group.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | [1/1] dt-bindings: regulators: Add missing regulator names | expand |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | success | |
| robh/dtbs-check | warning | build log |
| robh/dt-meta-schema | success |
On Wed, Jan 19, 2022 at 11:37:47AM +0100, Alexander Stein wrote: > The valid regulator names for the subnodes does not match the ones > mentioned in the description. > PFUZE3000 & PFUZE3001 uses 'v33', 'vccsd' and 'vldo[1-4]' as well, so > add them to the allowed node names. Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.
On Wed, 19 Jan 2022 11:37:47 +0100, Alexander Stein wrote: > The valid regulator names for the subnodes does not match the ones > mentioned in the description. > PFUZE3000 & PFUZE3001 uses 'v33', 'vccsd' and 'vldo[1-4]' as well, so > add them to the allowed node names. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] dt-bindings: regulators: Add missing regulator names commit: 8e9977e48c7c2a49e09859456dcba12a8d804a51 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
diff --git a/Documentation/devicetree/bindings/regulator/pfuze100.yaml b/Documentation/devicetree/bindings/regulator/pfuze100.yaml index f578e72778a7..a26bbd68b729 100644 --- a/Documentation/devicetree/bindings/regulator/pfuze100.yaml +++ b/Documentation/devicetree/bindings/regulator/pfuze100.yaml @@ -70,7 +70,11 @@ properties: $ref: "regulator.yaml#" type: object - "^(vsnvs|vref|vrefddr|swbst|coin)$": + "^vldo[1-4]$": + $ref: "regulator.yaml#" + type: object + + "^(vsnvs|vref|vrefddr|swbst|coin|v33|vccsd)$": $ref: "regulator.yaml#" type: object
The valid regulator names for the subnodes does not match the ones mentioned in the description. PFUZE3000 & PFUZE3001 uses 'v33', 'vccsd' and 'vldo[1-4]' as well, so add them to the allowed node names. Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com> --- This fixes warnings like: arch/arm/boot/dts/imx6ul-ccimx6ulsbcpro.dt.yaml: pmic@8: regulators: 'v33', 'vccsd', 'vcoin', 'vldo1', 'vldo2', 'vldo3', 'vldo4' do not match any of the regexes: '^(vsnvs|vref|vrefddr|swbst|coin)$', '^sw([1-4]|[1-4][a-c]|[1-4][a-c][a-c])$', '^vgen[1-6]$', 'pinctrl-[0-9]+' Documentation/devicetree/bindings/regulator/pfuze100.yaml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)