From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexandru Hossu <hossu.alexandru@gmail.com>, robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
gregkh@linuxfoundation.org, jollys@xilinx.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: axis-fifo: fix alignment and add DT binding documentation
Date: Wed, 4 Mar 2026 13:32:07 +0100 [thread overview]
Message-ID: <0eea78fe-59ab-4ca0-9e29-d68fa298ac09@kernel.org> (raw)
In-Reply-To: <ae0a95f4-8dac-4690-8810-79ad5fee7895@gmail.com>
On 04/03/2026 12:08, Alexandru Hossu wrote:
> Add YAML device tree binding documentation for the Xilinx
> AXI-Stream FIFO IP core and fix code alignment issue.
>
> Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
No patch here. Please use b4 to post patches.
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-04 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 11:08 [PATCH] staging: axis-fifo: fix alignment and add DT binding documentation Alexandru Hossu
2026-03-04 12:30 ` Rob Herring (Arm)
2026-03-04 12:32 ` Krzysztof Kozlowski [this message]
2026-03-04 12:46 ` [PATCH v2] dt-bindings: misc: xlnx,axi-fifo-mm-s: fix interrupt-parent property Alexandru Hossu
2026-03-04 12:51 ` Krzysztof Kozlowski
2026-03-04 12:52 ` Krzysztof Kozlowski
2026-03-04 13:16 ` [PATCH] " Alexandru Hossu
2026-03-04 13:22 ` Greg KH
2026-03-04 13:29 ` Conor Dooley
2026-03-04 14:08 ` Krzysztof Kozlowski
2026-03-04 14:22 ` Conor Dooley
2026-03-04 13:24 ` Krzysztof Kozlowski
2026-03-04 13:29 ` Alexandru Hossu
2026-03-04 14:12 ` [PATCH v2] " Dan Carpenter
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=0eea78fe-59ab-4ca0-9e29-d68fa298ac09@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hossu.alexandru@gmail.com \
--cc=jollys@xilinx.com \
--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 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.