From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Fabio Estevam <festevam@gmail.com>,
heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Fabio Estevam <festevam@nabladev.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 07/11] dt-bindings: serial: snps-dw-apb-uart: Add support for RV1103B
Date: Sat, 7 Feb 2026 12:09:36 +0100 [thread overview]
Message-ID: <2026020723-despise-panoramic-2bef@gregkh> (raw)
In-Reply-To: <20260207-unselfish-gorgeous-duck-cfc1ce@quoll>
On Sat, Feb 07, 2026 at 11:59:06AM +0100, Krzysztof Kozlowski wrote:
> On Fri, Feb 06, 2026 at 03:13:05PM -0300, Fabio Estevam wrote:
> > From: Fabio Estevam <festevam@nabladev.com>
> >
> > The UART used in the RV1103B SoC is still the same dw-apb-uart compatible
> > type as on the SoCs that came before, so add the RV1103B to the list
> > of variants.
> >
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: linux-serial@vger.kernel.org
> > Signed-off-by: Fabio Estevam <festevam@nabladev.com>
>
> Greg expressed MANY times that patches for him should be sent
> separately.
It's easy, I just ignore them now :)
next prev parent reply other threads:[~2026-02-07 11:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 18:12 [PATCH 00/11] ARM: rockchip: Add initial RV1103B and Omega4 board support Fabio Estevam
2026-02-06 18:12 ` [PATCH 01/11] dt-bindings: clock: rockchip: Add RV1103B clock and reset unit Fabio Estevam
2026-02-07 10:54 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 02/11] dt-bindings: clk: rockchip: Add RV1103B clock header Fabio Estevam
2026-02-06 20:15 ` Jonas Karlman
2026-02-07 11:00 ` Krzysztof Kozlowski
2026-02-07 11:01 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 03/11] clk: rockchip: Add clock controller for the RV1103B Fabio Estevam
2026-02-06 18:13 ` [PATCH 04/11] dt-bindings: pinctrl: Add RV1103B pinctrl support Fabio Estevam
2026-02-06 18:13 ` [PATCH 05/11] pinctrl: rockchip: " Fabio Estevam
2026-02-06 18:13 ` [PATCH 06/11] dt-bindings: mmc: rockchip-dw-mshc: Add compatible string for R1103B Fabio Estevam
2026-02-07 10:58 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 07/11] dt-bindings: serial: snps-dw-apb-uart: Add support for RV1103B Fabio Estevam
2026-02-07 10:59 ` Krzysztof Kozlowski
2026-02-07 11:09 ` Greg Kroah-Hartman [this message]
2026-02-06 18:13 ` [PATCH 08/11] dt-bindings: soc: rockchip: Add RV1103B IOC and GRF entries Fabio Estevam
2026-02-07 11:03 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 09/11] ARM: dts: rockchip: Add support for RV1103B Fabio Estevam
2026-02-06 18:13 ` [PATCH 10/11] dt-bindings: arm: rockchip: Add Onion RV1103B Omega4 Fabio Estevam
2026-02-07 10:56 ` Krzysztof Kozlowski
2026-02-06 18:13 ` [PATCH 11/11] ARM: dts: " Fabio Estevam
2026-02-06 20:50 ` Jonas Karlman
2026-02-07 10:55 ` [PATCH 00/11] ARM: rockchip: Add initial RV1103B and Omega4 board support 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=2026020723-despise-panoramic-2bef@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
/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