From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Julian Ribbeck <julian.ribbeck@gmx.de>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: arm: sunxi: Add itead,iteaduino-plus-a20
Date: Thu, 28 Sep 2023 06:41:17 +0200 [thread overview]
Message-ID: <56c4b1b8-3f96-463e-8d49-a17a11ebfe74@linaro.org> (raw)
In-Reply-To: <CVTLLDPXFP5D.ANP0YTD5AD0P@x1-yoga-arch>
On 27/09/2023 11:38, Julian Ribbeck wrote:
> Hi,
>
> I'm not totally familiar with the process here, but it seems like my
> patch was kind of forgotten? What should I do now? Is anything still
> missing?
Cc-ing maintainers is missing. Don't expect people you do no CC, to
magically pick up patches. :/
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-28 4:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 17:27 [PATCH] ARM: dts: sun7i: Add Iteaduino Plus A20 Julian Ribbeck
2023-06-17 17:41 ` Krzysztof Kozlowski
2023-06-17 20:51 ` Julian Ribbeck
2023-06-17 20:55 ` [PATCH v2 1/2] " Julian Ribbeck
2023-06-17 20:55 ` [PATCH v2 2/2] dt-bindings: arm: sunxi: Add itead,iteaduino-plus-a20 Julian Ribbeck
2023-06-18 8:00 ` Krzysztof Kozlowski
2023-09-27 9:38 ` Julian Ribbeck
2023-09-27 15:02 ` Conor Dooley
2023-09-28 4:41 ` Krzysztof Kozlowski [this message]
2023-09-27 20:44 ` Samuel Holland
2023-09-27 21:19 ` [PATCH v2 1/2] ARM: dts: sun7i: Add Iteaduino Plus A20 Samuel Holland
2023-09-28 16:57 ` [PATCH v3 " Julian Ribbeck
2023-09-28 16:57 ` [PATCH v3 2/2] dt-bindings: arm: sunxi: Add itead,iteaduino-plus-a20 Julian Ribbeck
2023-09-29 14:20 ` Conor Dooley
2023-10-06 9:01 ` [PATCH v4 1/2] ARM: dts: sun7i: Add Iteaduino Plus A20 Julian Ribbeck
2023-10-06 9:01 ` [PATCH v4 2/2] dt-bindings: arm: sunxi: Add itead,iteaduino-plus-a20 Julian Ribbeck
2023-10-13 19:18 ` [PATCH v4 1/2] ARM: dts: sun7i: Add Iteaduino Plus A20 Jernej Škrabec
2023-10-13 19:21 ` Jernej Škrabec
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=56c4b1b8-3f96-463e-8d49-a17a11ebfe74@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=julian.ribbeck@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).