public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: LiangCheng Wang <zaq14760@gmail.com>
Cc: drm@lists.freedesktop.org, devicetree@vger.kernel.org,
	noralf@tronnes.org, robh+dt@kernel.org, onlywig@gmail.com,
	cip-dev@lists.cip-project.org, conor@kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: display: Add MAYQUEEN PIXPAPER e-ink panel
Date: Fri, 20 Jun 2025 09:28:32 +0200	[thread overview]
Message-ID: <615522b2-544f-487d-aeb1-5ba069c322cd@kernel.org> (raw)
In-Reply-To: <20250620071825.741903-2-zaq14760@gmail.com>

On 20/06/2025 09:18, LiangCheng Wang wrote:
> The binding is for the MAYQUEEN PIXPAPER e-ink display panel,
> controlled via an SPI interface.
> 
> Signed-off-by: LiangCheng Wang <zaq14760@gmail.com>
> ---

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
</form letter>

Important from above:

"ancient tree (don't, instead use mainline) or work on fork of kernel"

That's exactly what you did.

Best regards,
Krzysztof


  reply	other threads:[~2025-06-23  4:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  3:37 [PATCH 0/3] drm/tiny: Add MAYQUEEN PIXPAPER e-ink panel support LiangCheng Wang
2025-06-18  3:37 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Mayqueen name LiangCheng Wang
2025-06-19 15:36   ` Conor Dooley
2025-06-18  3:37 ` [PATCH 2/3] drm: tiny: Add support for PIXPAPER e-ink panel LiangCheng Wang
2025-06-18  3:37 ` [PATCH 3/3] dt-bindings: display: Add MAYQUEEN " LiangCheng Wang
2025-06-19 15:43   ` Conor Dooley
2025-06-19 16:01     ` Krzysztof Kozlowski
2025-06-19 16:11       ` Conor Dooley
2025-06-20  3:48     ` lcwang
2025-06-20  3:53     ` lcwang
2025-06-20  3:53       ` [PATCH 3/3] dt-bindings: display: Add Mayqueen Pixpaper " lcwang
2025-06-20  5:28         ` Krzysztof Kozlowski
2025-06-20  7:18       ` [PATCH v2 0/3] drm/tiny: Add MAYQUEEN PIXPAPER e-ink panel support LiangCheng Wang
2025-06-20  7:27         ` Krzysztof Kozlowski
2025-06-20  7:18       ` [PATCH v2 3/3] dt-bindings: display: Add MAYQUEEN PIXPAPER e-ink panel LiangCheng Wang
2025-06-20  7:28         ` Krzysztof Kozlowski [this message]
2025-06-20  8:06           ` LiangCheng Wang
2025-06-20  8:26             ` Krzysztof Kozlowski

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=615522b2-544f-487d-aeb1-5ba069c322cd@kernel.org \
    --to=krzk@kernel.org \
    --cc=cip-dev@lists.cip-project.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drm@lists.freedesktop.org \
    --cc=noralf@tronnes.org \
    --cc=onlywig@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=zaq14760@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