From: Rob Herring <robh@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Sean Anderson <sean.anderson@seco.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] dt-bindings: xilinx: Remove uartlite from xilinx.txt
Date: Mon, 3 Feb 2025 12:28:59 -0600 [thread overview]
Message-ID: <20250203182859.GA3352680-robh@kernel.org> (raw)
In-Reply-To: <aa0b7f9a851c6b8d11f37050f84e0ec69cfa72a2.1738600116.git.michal.simek@amd.com>
On Mon, Feb 03, 2025 at 05:28:38PM +0100, Michal Simek wrote:
> current-speed description has been added to uartlite description by commit
> 3de536a8c365 ("dt-bindings: serial: uartlite: Add properties for
> synthesis-time parameters") that's why no reason to have in xilinx.txt too.
>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
>
> Fixes: 3de536a8c365 ("dt-bindings: serial: uartlite: Add properties for synthesis-time parameters")
Should not have a blank line in between and Fixes goes first. Will fixup
when applying.
Rob
next prev parent reply other threads:[~2025-02-03 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 16:28 [PATCH 0/3] dt-bindings: xilinx: Remove old descriptions Michal Simek
2025-02-03 16:28 ` [PATCH 1/3] dt-bindings: xilinx: Remove uartlite from xilinx.txt Michal Simek
2025-02-03 17:01 ` Sean Anderson
2025-02-03 18:28 ` Rob Herring [this message]
2025-02-03 18:29 ` Rob Herring (Arm)
2025-02-03 16:28 ` [PATCH 2/3] dt-bindings: xilinx: Remove description for SystemACE Michal Simek
2025-02-03 18:29 ` Rob Herring (Arm)
2025-02-03 16:28 ` [PATCH 3/3] dt-bindings: xilinx: Remove desciption for 16550 uart Michal Simek
2025-02-03 18:30 ` Rob Herring (Arm)
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=20250203182859.GA3352680-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=sean.anderson@seco.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).