From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@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,
Xilin Wu <wuxilin123@gmail.com>
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: Add AYN Technologies
Date: Sat, 21 Feb 2026 17:56:50 +0100 [thread overview]
Message-ID: <7a96a82a-f856-4bee-b4d5-2d1e71b92f23@kernel.org> (raw)
In-Reply-To: <CALHNRZ8JT34J024TvG77LW2vN03q9te+xXmR0e7DMOz3GqouEQ@mail.gmail.com>
On 21/02/2026 17:31, Aaron Kling wrote:
> On Sat, Feb 21, 2026 at 4:55 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Fri, Feb 20, 2026 at 04:11:11PM -0600, Aaron Kling wrote:
>>> From: Xilin Wu <wuxilin123@gmail.com>
>>>
>>> Add an entry for AYN Technologies (https://www.ayntec.com/)
>>>
>>> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>> ---
>>> This was originally submitted as part of the original Odin 2 submission
>>> [0], but that series stalled, so submitting this separately. The prefix
>>> was renamed to ayntec as per the review comment on that patch.
>>
>> And why do we want it without the rest? Answering: we don't want unused
>> binding and nothing in the commit msg explains other options.
>
> You have told me repeatedly to not do monolithic series that cross
> subsystems. So I am working through support for the AYN qcs8550
So why is this patch not with the rest for the same subsystem?
> devices and splitting that into a bunch of different series. Several
> of those independently reference this vendor prefix and may progress
Which one? I see only one in the patchset pointed by [0]. I really do
not understand why you are doing it completely different than every
other upstreaming which you can find on lore.
> in any order, so this needs submitted separately. I am submitting it
> early to try to get it in before the rest are ready, so I don't have
> to list this as a dependency to all of them.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-21 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 22:11 Aaron Kling via B4 Relay
2026-02-21 10:55 ` Krzysztof Kozlowski
2026-02-21 16:31 ` Aaron Kling
2026-02-21 16:56 ` Krzysztof Kozlowski [this message]
2026-02-21 17:22 ` Aaron Kling
2026-03-23 17:01 ` Aaron Kling
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=7a96a82a-f856-4bee-b4d5-2d1e71b92f23@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=webgeek1234@gmail.com \
--cc=wuxilin123@gmail.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
all inboxes | Powered by JetHome®