From: Saalim Quadri <danascape@gmail.com>
To: jikos@kernel.org
Cc: bentiss@kernel.org, danascape@gmail.com,
gregkh@linuxfoundation.org, lains@riseup.net,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Writing a Driver for Xinmeng M71 Keyboard (Battery Status Support)
Date: Mon, 23 Jun 2025 18:33:33 +0530 [thread overview]
Message-ID: <20250623130333.330397-1-danascape@gmail.com> (raw)
In-Reply-To: <2n706qq8-45os-9959-7427-83r26344q434@xreary.bet>
Thank you very much for the response,
I was able to parse the raw event and get the data, I am currently trying to figure out how to fetch the data on-demand and read the values,
I took hid-kysona as reference.
I will be sending a patch soon for reviews
Thank you very much,
Sincerely,
Saalim Quadri
prev parent reply other threads:[~2025-06-23 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 11:32 [RFC] Writing a Driver for Xinmeng M71 Keyboard (Battery Status Support) Saalim Quadri
2025-06-22 21:02 ` Jiri Kosina
2025-06-23 13:03 ` Saalim Quadri [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=20250623130333.330397-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=bentiss@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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).