From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel28972897 <danyboy28sep@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 0/2] dt-bindings: misc: convert axis-fifo binding to YAML
Date: Sat, 19 Sep 2026 08:47:57 +0100 [thread overview]
Message-ID: <2026091930-resume-ascension-2fe2@gregkh> (raw)
In-Reply-To: <20260919025900.169703-1-danyboy28sep@gmail.com>
On Fri, Sep 18, 2026 at 08:58:58PM -0600, Daniel28972897 wrote:
> This is v2 of the axis-fifo devicetree binding conversion, addressing
> review feedback from the Sashiko AI bot on v1:
>
> - The FIFO depth properties are documented in 32-bit words, not bytes,
> matching the original text binding and the driver's own arithmetic.
> - additionalProperties: false no longer rejects real-world devicetrees,
> since all properties generated by the Xilinx IP integrator (even
> ones the driver ignores) are now listed in the schema.
> - The now-superseded drivers/staging/axis-fifo/axis-fifo.txt is
> removed, split into its own patch per
> Documentation/devicetree/bindings/submitting-patches.rst.
>
> Daniel28972897 (2):
Again, you were told this type of change was not ok, please do not
ignore review comments. Also, this isn't a valid author name :)
thanks,
greg k-h
prev parent reply other threads:[~2026-09-19 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 1:14 [PATCH] dt-bindings: misc: add binding for Xilinx AXI4-Stream FIFO MM S Daniel28972897
2026-09-19 2:58 ` [PATCH v2 0/2] dt-bindings: misc: convert axis-fifo binding to YAML Daniel28972897
2026-09-19 2:58 ` [PATCH v2 1/2] " Daniel28972897
2026-09-19 6:58 ` Krzysztof Kozlowski
2026-09-19 2:59 ` [PATCH v2 2/2] staging: axis-fifo: remove superseded text binding Daniel28972897
2026-09-19 6:59 ` Krzysztof Kozlowski
2026-09-19 7:47 ` Greg Kroah-Hartman [this message]
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=2026091930-resume-ascension-2fe2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor+dt@kernel.org \
--cc=danyboy28sep@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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
all inboxes | Powered by JetHome®