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>, cip-dev@lists.cip-project.org
Cc: drm@lists.freedesktop.org, devicetree@vger.kernel.org,
	noralf@tronnes.org, robh+dt@kernel.org, onlywig@gmail.com
Subject: Re: [PATCH 0/3] drm/tiny: Add MAYQUEEN PIXPAPER e-ink panel support
Date: Wed, 18 Jun 2025 08:14:45 +0200	[thread overview]
Message-ID: <2f4a72d6-d0aa-4364-be61-a8c2263e194c@kernel.org> (raw)
In-Reply-To: <20250618034936.172150-1-zaq14760@gmail.com>

On 18/06/2025 05:49, LiangCheng Wang wrote:
> This series adds support for the MAYQUEEN PIXPAPER e-ink panel
> (122x250 pixels, SPI-controlled) to the tiny drm subsystem.
> 
> Patches (must be applied in order due to dependencies):
> Patch 1/3: Adds 'mayqueen' vendor prefix.
> Patch 2/3: Implements PIXPAPER tiny drm driver.
> Patch 3/3: Adds PIXPAPER device tree bindings.
> 
> Tested on PIXPAPER hardware with linux-5.10.y-cip,
> verifying display initialization and refresh.
> All patches pass checkpatch.pl.
> 
> Signed-off-by: Wig Cheng <onlywig@gmail.com>
> Signed-off-by: LiangCheng Wang <zaq14760@gmail.com>
> 

I don't understand this CC list. Cip is for sure incorrect... unless you
target CIP, but such patches must not be sent to upstream because that
would be waste of our time.

<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>

Best regards,
Krzysztof


  parent reply	other threads:[~2025-06-18  9:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18  3:49 [PATCH 0/3] drm/tiny: Add MAYQUEEN PIXPAPER e-ink panel support LiangCheng Wang
2025-06-18  3:49 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Mayqueen name LiangCheng Wang
2025-06-18  3:49 ` [PATCH 2/3] drm: tiny: Add support for PIXPAPER e-ink panel LiangCheng Wang
2025-06-18  3:49 ` [PATCH 3/3] dt-bindings: display: Add MAYQUEEN " LiangCheng Wang
2025-06-18  6:13   ` Krzysztof Kozlowski
2025-06-18  6:14 ` Krzysztof Kozlowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-18  3:37 [PATCH 0/3] drm/tiny: Add MAYQUEEN PIXPAPER e-ink panel support LiangCheng Wang

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=2f4a72d6-d0aa-4364-be61-a8c2263e194c@kernel.org \
    --to=krzk@kernel.org \
    --cc=cip-dev@lists.cip-project.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