From: Wolfram Sang <wsa@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, joel@jms.id.au
Subject: Re: [PATCH v4 5/5] MAINTAINERS: Add HPE GXP I2C Support
Date: Sat, 28 Jan 2023 19:38:21 +0100 [thread overview]
Message-ID: <Y9VrnQxiFjVqtybb@ninjato> (raw)
In-Reply-To: <20230125184438.28483-6-nick.hawkins@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
On Wed, Jan 25, 2023 at 12:44:38PM -0600, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> Add the I2C controller source and bindings.
>
> Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
I assume this better goes via the arm-soc-tree as well to reduce merge
conflicts, so:
Acked-by: Wolfram Sang <wsa@kernel.org>
Let me know if I should pick this instead. Will review the driver in the
next days.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@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, joel@jms.id.au
Subject: Re: [PATCH v4 5/5] MAINTAINERS: Add HPE GXP I2C Support
Date: Sat, 28 Jan 2023 19:38:21 +0100 [thread overview]
Message-ID: <Y9VrnQxiFjVqtybb@ninjato> (raw)
In-Reply-To: <20230125184438.28483-6-nick.hawkins@hpe.com>
[-- Attachment #1.1: Type: text/plain, Size: 448 bytes --]
On Wed, Jan 25, 2023 at 12:44:38PM -0600, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> Add the I2C controller source and bindings.
>
> Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
I assume this better goes via the arm-soc-tree as well to reduce merge
conflicts, so:
Acked-by: Wolfram Sang <wsa@kernel.org>
Let me know if I should pick this instead. Will review the driver in the
next days.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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
next prev parent reply other threads:[~2023-01-28 18:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:44 [PATCH v4 0/5] ARM: Add GXP I2C Support nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-01-25 18:44 ` [PATCH v4 1/5] i2c: hpe: Add GXP SoC I2C Controller nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-02-15 20:29 ` Wolfram Sang
2023-02-15 20:29 ` Wolfram Sang
2023-02-16 20:02 ` Hawkins, Nick
2023-02-16 20:02 ` Hawkins, Nick
2023-02-16 20:47 ` Wolfram Sang
2023-02-16 20:47 ` Wolfram Sang
2023-01-25 18:44 ` [PATCH v4 2/5] dt-bindings: i2c: Add hpe,gxp-i2c nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-01-25 21:18 ` Rob Herring
2023-01-25 21:18 ` Rob Herring
2023-01-25 21:31 ` Hawkins, Nick
2023-01-25 21:31 ` Hawkins, Nick
2023-01-26 13:38 ` Rob Herring
2023-01-26 13:38 ` Rob Herring
2023-01-25 18:44 ` [PATCH v4 3/5] ARM: dts: hpe: Add I2C Topology nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-01-25 18:44 ` [PATCH v4 4/5] ARM: multi_v7_defconfig: add gxp i2c module nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-01-25 18:44 ` [PATCH v4 5/5] MAINTAINERS: Add HPE GXP I2C Support nick.hawkins
2023-01-25 18:44 ` nick.hawkins
2023-01-28 18:38 ` Wolfram Sang [this message]
2023-01-28 18:38 ` Wolfram Sang
2023-02-07 21:53 ` Hawkins, Nick
2023-02-07 21:53 ` Hawkins, Nick
2023-02-15 19:26 ` Hawkins, Nick
2023-02-15 19:26 ` Hawkins, Nick
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=Y9VrnQxiFjVqtybb@ninjato \
--to=wsa@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--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 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.