From: Lee Jones <lee@kernel.org>
To: nick.hawkins@hpe.com
Cc: verdun@hpe.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux@armlinux.org.uk,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 3/6] dt-bindings: mfd: syscon: Document GXP register compatible
Date: Wed, 4 Jan 2023 17:20:42 +0000 [thread overview]
Message-ID: <Y7W1aiMRolW0UTqd@google.com> (raw)
In-Reply-To: <20221216183532.78933-4-nick.hawkins@hpe.com>
On Fri, 16 Dec 2022, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> Document hpe,gxp-sysreg compatible for GXP registers.
>
> Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks
--
Lee Jones [李琼斯]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-04 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 18:35 [PATCH v1 0/6] ARM: Add GXP I2C Support nick.hawkins
2022-12-16 18:35 ` [PATCH v1 1/6] i2c: hpe: Add GXP SoC I2C Controller nick.hawkins
2022-12-17 10:51 ` Krzysztof Kozlowski
2023-01-09 20:23 ` Hawkins, Nick
2023-01-10 8:35 ` Krzysztof Kozlowski
2022-12-16 18:35 ` [PATCH v1 2/6] dt-bindings: i2c: hpe,gxp-i2c nick.hawkins
2022-12-17 10:55 ` Krzysztof Kozlowski
2022-12-16 18:35 ` [PATCH v1 3/6] dt-bindings: mfd: syscon: Document GXP register compatible nick.hawkins
2022-12-17 10:59 ` Krzysztof Kozlowski
2023-01-04 17:20 ` Lee Jones [this message]
2022-12-16 18:35 ` [PATCH v1 4/6] ARM: dts: hpe: Add I2C Topology nick.hawkins
2022-12-17 10:58 ` Krzysztof Kozlowski
2022-12-16 18:35 ` [PATCH v1 5/6] ARM: multi_v7_defconfig: add gxp i2c module nick.hawkins
2022-12-16 18:35 ` [PATCH v1 6/6] MAINTAINERS: Add HPE GXP I2C Support nick.hawkins
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=Y7W1aiMRolW0UTqd@google.com \
--to=lee@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nick.hawkins@hpe.com \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.com \
/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;
as well as URLs for NNTP newsgroup(s).