From: Jiri Kosina <jikos@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Marco Morandini <marco.morandini@polimi.it>,
Peter Hutterer <peter.hutterer@who-t.net>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v3] HID: Add introduction about HID for non-kernel programmers
Date: Mon, 7 Aug 2023 13:25:46 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2308071325150.14207@cbobk.fhfr.pm> (raw)
In-Reply-To: <87lef9c8jz.fsf@meer.lwn.net>
On Fri, 21 Jul 2023, Jonathan Corbet wrote:
> > Add an introduction about HID meant for the casual programmer
> > that is trying either to fix his device or to understand
> > what is going wrong.
> >
> > Signed-off-by: Marco Morandini <marco.morandini@polimi.it>
> > Co-authored-by: Peter Hutterer <peter.hutterer@who-t.net>
> > ---
> > v2: https://lore.kernel.org/linux-input/70fdef05-d3b8-e24b-77be-901bd5be369e@polimi.it/
> >
> > changes:
> > - corrections suggested in https://lore.kernel.org/linux-input/20230627060437.GA726439@quokka/
> > - corrections suggested in https://lore.kernel.org/linux-input/f53e756f-7c81-1c79-23ea-b9009fdd2ef4@infradead.org/
> > - corrections suggested in https://lore.kernel.org/linux-input/20230710021034.GA600582@quokka/
> > - corrections suggested in https://lore.kernel.org/linux-input/20230717001544.GA129954@quokka/
> > - some rewording of Documentation/hid/hidreport-parsing.rst
> >
> > Documentation/hid/hidintro.rst | 524 ++++++++++++++++++++++++
> > Documentation/hid/hidreport-parsing.rst | 49 +++
> > Documentation/hid/index.rst | 1 +
> > include/linux/hid.h | 23 ++
> > 4 files changed, 597 insertions(+)
> > create mode 100644 Documentation/hid/hidintro.rst
> > create mode 100644 Documentation/hid/hidreport-parsing.rst
>
> Is there a plan for this patch? Please let me know if I should take it
> through the docs tree.
I have now queued this in hid.git#for-6.5/doc. Sorry for the delay, I was
off for pretty much whole July, and it takes time to go through all the
things that accumulated.
Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2023-08-07 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 16:40 [PATCH v3] HID: Add introduction about HID for non-kernel programmers Marco Morandini
2023-07-21 20:29 ` Jonathan Corbet
2023-08-07 11:25 ` Jiri Kosina [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=nycvar.YFH.7.76.2308071325150.14207@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marco.morandini@polimi.it \
--cc=peter.hutterer@who-t.net \
/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).