devicetree.vger.kernel.org archive mirror
 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, conor@kernel.org,
	onlywig@gmail.com, cip-dev@lists.cip-project.org
Subject: Re: [PATCH v2 3/3] dt-bindings: display: Add MAYQUEEN PIXPAPER e-ink panel
Date: Fri, 20 Jun 2025 10:26:21 +0200	[thread overview]
Message-ID: <97fc47af-82ed-41e4-8824-02b1b817d967@kernel.org> (raw)
In-Reply-To: <20250620080629.743266-1-zaq14760@gmail.com>

On 20/06/2025 10:06, LiangCheng Wang wrote:
> Dear Krzysztof,
> 
> Thank you very much for your review and feedback.
> I sincerely apologize for the issue with my emails bouncing.
> As a newcomer to using `git send-email`, I was unaware of this problem,
> particularly because I did not receive any bounce notifications in my Gmail inbox or spam folder.
> This made it difficult for me to identify the issue promptly.
> 
> Following your advice, I am migrating my driver development to the latest kernel (e.g., v6.12)
> and will use the `get_maintainer.pl` script from that kernel to ensure the correct Cc list.
> I am also reviewing my `git send-email` configuration to prevent further email delivery issues.
> 
> Could you kindly provide more details about the email bounce issue, such as specific error messages,
> problematic recipient addresses, or any other relevant information?
> This would help me pinpoint and resolve the issue more effectively.

Every email here bounces from non-existing drm list.

 <drm@lists.freedesktop.org>: unknown user: "drm"

> Additionally, if you have any tips on configuring `git send-email`
> or the patch submission process, I would greatly appreciate your guidance.
> 


Best regards,
Krzysztof

      reply	other threads:[~2025-06-20  8:26 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
2025-06-20  8:06           ` LiangCheng Wang
2025-06-20  8:26             ` Krzysztof Kozlowski [this message]

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=97fc47af-82ed-41e4-8824-02b1b817d967@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;
as well as URLs for NNTP newsgroup(s).