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 v2] dt-bindings: misc: xlnx,axi-fifo-mm-s: fix interrupt-parent property
Date: Wed, 4 Mar 2026 13:52:33 +0100 [thread overview]
Message-ID: <e6f8db4d-2a5a-4424-b44d-6416ee0c5ca0@kernel.org> (raw)
In-Reply-To: <fe1f9d67-7176-476e-8c76-afcc7595cde1@kernel.org>
On 04/03/2026 13:51, Krzysztof Kozlowski wrote:
> On 04/03/2026 13:46, Alexandru Hossu wrote:
>> v2: Remove interrupt-parent property declaration as it is a standard
>> property that does not need to be explicitly defined in the binding.
>>
>> Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
>
>
> Stop and read the feedback.
>
> There is still no patch!
Look here:
https://lore.kernel.org/lkml/fbb68131-03ab-460b-8d11-e4892d91807f@gmail.com/
No patch inline, just separate attachment. That's not something possible
to review.
And another point is:
Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-04 12:52 UTC|newest]
Thread overview: 13+ 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
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 [this message]
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 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=e6f8db4d-2a5a-4424-b44d-6416ee0c5ca0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox