From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-i2c@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-serial@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 6/7] dt-bindings: serial: renesas,scif: R-Car V3U is R-Car Gen4
Date: Wed, 4 May 2022 21:38:44 +0200 [thread overview]
Message-ID: <YnLWRBd+0mBz2Mlu@kunai> (raw)
In-Reply-To: <c57ed00e85778380776330be6183c6861d843c22.1651497024.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 342 bytes --]
On Mon, May 02, 2022 at 03:34:58PM +0200, Geert Uytterhoeven wrote:
> Despite the name, R-Car V3U is the first member of the R-Car Gen4
> family. Hence move its compatible value to the R-Car Gen4 section.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: devicetree@vger.kernel.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
iommu@lists.linux-foundation.org,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-i2c@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
dmaengine@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Will Deacon <will@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 6/7] dt-bindings: serial: renesas,scif: R-Car V3U is R-Car Gen4
Date: Wed, 4 May 2022 21:38:44 +0200 [thread overview]
Message-ID: <YnLWRBd+0mBz2Mlu@kunai> (raw)
In-Reply-To: <c57ed00e85778380776330be6183c6861d843c22.1651497024.git.geert+renesas@glider.be>
[-- Attachment #1.1: Type: text/plain, Size: 342 bytes --]
On Mon, May 02, 2022 at 03:34:58PM +0200, Geert Uytterhoeven wrote:
> Despite the name, R-Car V3U is the first member of the R-Car Gen4
> family. Hence move its compatible value to the R-Car Gen4 section.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-05-04 19:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 13:34 [PATCH 0/7] dt-bindings: renesas: R-Car V3U is R-Car Gen4 Geert Uytterhoeven
2022-05-02 13:34 ` Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 1/7] dt-bindings: gpio: renesas,rcar-gpio: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 1/7] dt-bindings: gpio: renesas, rcar-gpio: " Geert Uytterhoeven
2022-05-03 13:01 ` [PATCH 1/7] dt-bindings: gpio: renesas,rcar-gpio: " Krzysztof Kozlowski
2022-05-03 13:01 ` Krzysztof Kozlowski
2022-05-04 19:37 ` Wolfram Sang
2022-05-04 19:37 ` Wolfram Sang
2022-05-05 13:04 ` Bartosz Golaszewski
2022-05-05 13:04 ` Bartosz Golaszewski
2022-05-02 13:34 ` [PATCH 2/7] dt-bindings: i2c: renesas,rcar-i2c: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 2/7] dt-bindings: i2c: renesas, rcar-i2c: " Geert Uytterhoeven
2022-05-03 13:01 ` [PATCH 2/7] dt-bindings: i2c: renesas,rcar-i2c: " Krzysztof Kozlowski
2022-05-03 13:01 ` Krzysztof Kozlowski
2022-05-04 19:38 ` Wolfram Sang
2022-05-04 19:38 ` Wolfram Sang
2022-05-04 19:51 ` Wolfram Sang
2022-05-04 19:51 ` Wolfram Sang
2022-05-02 13:34 ` [PATCH 3/7] dt-bindings: iommu: renesas,ipmmu-vmsa: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 3/7] dt-bindings: iommu: renesas, ipmmu-vmsa: " Geert Uytterhoeven
2022-05-03 13:01 ` [PATCH 3/7] dt-bindings: iommu: renesas,ipmmu-vmsa: " Krzysztof Kozlowski
2022-05-03 13:01 ` [PATCH 3/7] dt-bindings: iommu: renesas, ipmmu-vmsa: " Krzysztof Kozlowski
2022-05-04 8:37 ` [PATCH 3/7] dt-bindings: iommu: renesas,ipmmu-vmsa: " Joerg Roedel
2022-05-04 8:37 ` [PATCH 3/7] dt-bindings: iommu: renesas, ipmmu-vmsa: " Joerg Roedel
2022-05-04 19:38 ` [PATCH 3/7] dt-bindings: iommu: renesas,ipmmu-vmsa: " Wolfram Sang
2022-05-04 19:38 ` [PATCH 3/7] dt-bindings: iommu: renesas, ipmmu-vmsa: " Wolfram Sang
2022-05-02 13:34 ` [PATCH 4/7] dt-bindings: renesas,rcar-dmac: " Geert Uytterhoeven
2022-05-02 13:34 ` Geert Uytterhoeven
2022-05-03 13:02 ` Krzysztof Kozlowski
2022-05-03 13:02 ` Krzysztof Kozlowski
2022-05-16 11:31 ` Vinod Koul
2022-05-16 11:31 ` Vinod Koul
2022-05-02 13:34 ` [PATCH 5/7] dt-bindings: serial: renesas,hscif: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 5/7] dt-bindings: serial: renesas, hscif: " Geert Uytterhoeven
2022-05-03 13:02 ` [PATCH 5/7] dt-bindings: serial: renesas,hscif: " Krzysztof Kozlowski
2022-05-03 13:02 ` Krzysztof Kozlowski
2022-05-04 19:38 ` Wolfram Sang
2022-05-04 19:38 ` Wolfram Sang
2022-05-02 13:34 ` [PATCH 6/7] dt-bindings: serial: renesas,scif: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 6/7] dt-bindings: serial: renesas, scif: " Geert Uytterhoeven
2022-05-03 13:02 ` [PATCH 6/7] dt-bindings: serial: renesas,scif: " Krzysztof Kozlowski
2022-05-03 13:02 ` [PATCH 6/7] dt-bindings: serial: renesas, scif: " Krzysztof Kozlowski
2022-05-04 19:38 ` Wolfram Sang [this message]
2022-05-04 19:38 ` [PATCH 6/7] dt-bindings: serial: renesas,scif: " Wolfram Sang
2022-05-02 13:34 ` [PATCH 7/7] dt-bindings: watchdog: renesas,wdt: " Geert Uytterhoeven
2022-05-02 13:34 ` [PATCH 7/7] dt-bindings: watchdog: renesas, wdt: " Geert Uytterhoeven
2022-05-03 13:02 ` [PATCH 7/7] dt-bindings: watchdog: renesas,wdt: " Krzysztof Kozlowski
2022-05-03 13:02 ` Krzysztof Kozlowski
2022-05-04 19:38 ` Wolfram Sang
2022-05-04 19:38 ` Wolfram Sang
2022-05-14 14:15 ` Guenter Roeck
2022-05-14 14:15 ` Guenter Roeck
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=YnLWRBd+0mBz2Mlu@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=yoshihiro.shimoda.uh@renesas.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.