From: Rob Herring <robh@kernel.org>
To: David Virag <virag.david003@gmail.com>
Cc: linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomasz Figa <tomasz.figa@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: samsung: Document Exynos7885
Date: Fri, 12 Nov 2021 09:29:35 -0600 [thread overview]
Message-ID: <YY6IX0FYGfdP11zR@robh.at.kernel.org> (raw)
In-Reply-To: <20211031231511.46856-1-virag.david003@gmail.com>
On Mon, 01 Nov 2021 00:15:11 +0100, David Virag wrote:
> Document compatible string for Exynos7885 SoC.
>
> Signed-off-by: David Virag <virag.david003@gmail.com>
> ---
> Changes in v2:
> - (none)
>
> Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: David Virag <virag.david003@gmail.com>
Cc: linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomasz Figa <tomasz.figa@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: pinctrl: samsung: Document Exynos7885
Date: Fri, 12 Nov 2021 09:29:35 -0600 [thread overview]
Message-ID: <YY6IX0FYGfdP11zR@robh.at.kernel.org> (raw)
In-Reply-To: <20211031231511.46856-1-virag.david003@gmail.com>
On Mon, 01 Nov 2021 00:15:11 +0100, David Virag wrote:
> Document compatible string for Exynos7885 SoC.
>
> Signed-off-by: David Virag <virag.david003@gmail.com>
> ---
> Changes in v2:
> - (none)
>
> Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
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:[~2021-11-12 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 23:15 [PATCH v2 1/2] dt-bindings: pinctrl: samsung: Document Exynos7885 David Virag
2021-10-31 23:15 ` David Virag
2021-10-31 23:17 ` [PATCH v2 2/2] pinctrl: samsung: Add Exynos7885 SoC specific data David Virag
2021-10-31 23:17 ` David Virag
2021-11-02 7:55 ` [PATCH v2 1/2] dt-bindings: pinctrl: samsung: Document Exynos7885 Krzysztof Kozlowski
2021-11-02 7:55 ` Krzysztof Kozlowski
2021-11-12 15:29 ` Rob Herring [this message]
2021-11-12 15:29 ` Rob Herring
2021-11-16 10:24 ` Krzysztof Kozlowski
2021-11-16 10:24 ` Krzysztof Kozlowski
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=YY6IX0FYGfdP11zR@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=virag.david003@gmail.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.