linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dean Camera <dean@fourwalledcubicle.com>
To: "Filipe Laíns" <lains@archlinux.org>,
	linux-input@vger.kernel.org, jikos@kernel.org,
	benjamin.tissoires@redhat.com
Subject: Re: [V3, PATCH] Add additional hidraw input/output report ioctls.
Date: Sat, 28 Nov 2020 18:02:55 +1100	[thread overview]
Message-ID: <c55b4ad5-9fb8-18ef-b931-38a4c37f445f@fourwalledcubicle.com> (raw)
In-Reply-To: <877bfbede4d3bbf40a91c8392218eeab6672e98c.camel@archlinux.org>

On 28/11/2020 7:11 am, Filipe Laíns wrote:
> 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.
> 

I completely understand - I maintain some open source projects myself, 
so I know how it is. I'm just a millenial used to pull requests, issue 
trackers and/or email attachments, so I wasn't too sure how to proceed 
here and didn't want to mis-step and end up with it getting lost due to 
my own inaction.

Thank you both sincerely for your time and efforts, they are very much 
appreciated.

> 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
> 

I do wish there was a way to track the patches a little better - I fully 
understand about the time pressures involved, but having a way to at 
least know it was seen and added to a backlog somewhere would be nice. 
Alas, I fear such talk is somewhat like the proverbial ocean boiling.

> Just one thing, in the kernel mailing lists you are discouraged to top-post.

Thanks for the advice, taken under consideration :).

> 
> 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
> 

Cheers!
- Dean

  reply	other threads:[~2020-11-28 22:05 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
2020-11-28  7:02           ` Dean Camera [this message]
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=c55b4ad5-9fb8-18ef-b931-38a4c37f445f@fourwalledcubicle.com \
    --to=dean@fourwalledcubicle.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=lains@archlinux.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).