From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: HP Dev <hphyperxdev@gmail.com>
Cc: carl.ng@hp.com, chris.toledanes@hp.com,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
maxwell.nguyen@hp.com
Subject: Re: [PATCH V2] Input: xpad - Add HyperX Clutch Gladiate Support
Date: Mon, 07 Aug 2023 09:24:55 -0700 [thread overview]
Message-ID: <87350uizvs.fsf@nvidia.com> (raw)
In-Reply-To: <20230804201926.10723-1-hphyperxdev@gmail.com> (HP Dev's message of "Fri, 4 Aug 2023 13:19:26 -0700")
On Fri, 04 Aug, 2023 13:19:26 -0700 HP Dev <hphyperxdev@gmail.com> wrote:
> Hi Rahul,
> Is there anything else we need to provide?
From what I can tell, this patch looks good now to me.
> When can we expect the patch to be rolled in?
This is up to the subsystem maintainers to manage. In the case of the
input subsystem, that would be Dmitry. Keep in mind the subsystem
maintainers are busy and persevere to help look at patches. I am sure he
will get to it in the future when he has a chance.
It's also ok to resend the patch or the patch series after a couple of
weeks with the word "RESEND" added to the subject line:
https://docs.kernel.org/process/submitting-patches.html#don-t-get-discouraged-or-impatient
If you need to do a RESEND for this patch after a couple weeks, feel
free to add my Reviewed-by to the git trailer in your commit message.
--
Thanks,
Rahul Rameshbabu
prev parent reply other threads:[~2023-08-07 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:49 [PATCH V2] Input: xpad - Add HyperX Clutch Gladiate Support HP Dev
2023-07-24 23:47 ` Rahul Rameshbabu
2023-08-04 20:19 ` HP Dev
2023-08-07 16:24 ` Rahul Rameshbabu [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=87350uizvs.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=carl.ng@hp.com \
--cc=chris.toledanes@hp.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hphyperxdev@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=maxwell.nguyen@hp.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).