From: "Filipe Laíns" <lains@archlinux.org>
To: Dean Camera <dean@fourwalledcubicle.com>,
linux-input@vger.kernel.org, jikos@kernel.org,
benjamin.tissoires@redhat.com
Subject: Re: [V3, PATCH] Add additional hidraw input/output report ioctls.
Date: Fri, 27 Nov 2020 20:11:21 +0000 [thread overview]
Message-ID: <877bfbede4d3bbf40a91c8392218eeab6672e98c.camel@archlinux.org> (raw)
In-Reply-To: <d295d0bf-9de7-9927-05b6-2897ada89c42@fourwalledcubicle.com>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On Fri, 2020-11-27 at 15:05 +1100, Dean Camera wrote:
> Thank you for the review, Filipe!
>
> I'm still new to the kernel patch submission process, so I'm a little
> perplexed by the next steps. Who will decide if it is to be applied, and
> is there any further action I need to take?
No worries :)
That'd probably Benjamin Tissoires, co-maintainer of the HID subsystem.
There is no further action you need to take, just wait. Please understand that
these things can sometimes take a while as maintainer time is limited and they
may have a long backlog to fight through.
Also be aware that maintainers might be a bit conservative about adding new
features as they will be required to maintain them in the long run, so don't
take it personally if they chose not to to merge some of your patches.
> I am obviously keen, but not impatient, to get this feature in. I'm
> happy to follow whatever process is required, I just haven't found
> anything beyond the initial "submitting your patch" documentation.
Yeah, I sympathize. The process essentially is to send the patch and wait :P
Just one thing, in the kernel mailing lists you are discouraged to top-post.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
> Cheers!
> - Dean
Cheers,
Filipe Laíns
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-27 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 22:39 [V3, PATCH] Add additional hidraw input/output report ioctls Dean Camera
2020-11-26 19:05 ` Filipe Laíns
2020-11-26 21:30 ` Dean Camera
2020-11-26 21:42 ` Filipe Laíns
2020-11-27 4:05 ` Dean Camera
2020-11-27 20:11 ` Filipe Laíns [this message]
2020-11-28 7:02 ` Dean Camera
2020-11-29 20:01 ` Filipe Laíns
2020-11-27 14:49 ` Jiri Kosina
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=877bfbede4d3bbf40a91c8392218eeab6672e98c.camel@archlinux.org \
--to=lains@archlinux.org \
--cc=benjamin.tissoires@redhat.com \
--cc=dean@fourwalledcubicle.com \
--cc=jikos@kernel.org \
--cc=linux-input@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).