linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Langyan Ye <yelangyan@huaqin.corp-partner.google.com>
To: dmitry.torokhov@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
	 conor+dt@kernel.org, jikos@kernel.org, bentiss@kernel.org
Cc: dianders@chromium.org, linux-input@vger.kernel.org,
	 devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add tc3408 bindings and timing
Date: Tue, 30 Sep 2025 16:21:56 +0800	[thread overview]
Message-ID: <CA++9cvrDRU4PStp82M0oz-ZtE-1fuPnMOEfMw4uv3wL1_DoYiQ@mail.gmail.com> (raw)
In-Reply-To: <CA++9cvojHApEr0b5ZbRNVjYtWvCS8WmZ-mrGMDh5O9mp1fkT0w@mail.gmail.com>

Hi,

Just a gentle ping on this 2-patch series:

  [1/2] https://patchwork.kernel.org/project/linux-input/patch/20250821031514.49497-2-yelangyan@huaqin.corp-partner.google.com/
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

  [2/2] https://patchwork.kernel.org/project/linux-input/patch/20250821031514.49497-3-yelangyan@huaqin.corp-partner.google.com/
    Reviewed-by: Douglas Anderson <dianders@chromium.org>

Both patches have been reviewed.
Is there anything else I should do to help get this series landed?

Thanks a lot!

Best regards,
Langyan

  reply	other threads:[~2025-09-30  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  3:15 [PATCH v2 0/2] Add tc3408 bindings and timing Langyan Ye
2025-08-21  3:15 ` [PATCH v2 1/2] dt-bindings: input: Add Parade TC3408 touchscreen controller Langyan Ye
2025-08-21  3:15 ` [PATCH v2 2/2] HID: i2c-hid: elan: Add parade-tc3408 timing Langyan Ye
2025-08-21 14:29   ` Doug Anderson
2025-08-21  3:44 ` [PATCH v2 0/2] Add tc3408 bindings and timing Langyan Ye
2025-09-30  8:21   ` Langyan Ye [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-20 12:25 Langyan Ye

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=CA++9cvrDRU4PStp82M0oz-ZtE-1fuPnMOEfMw4uv3wL1_DoYiQ@mail.gmail.com \
    --to=yelangyan@huaqin.corp-partner.google.com \
    --cc=bentiss@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).