public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Rosalie <rosalie@mailbox.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
	Sanjay Govind <sanjay.govind9@gmail.com>,
	Brenton Simpson <appsforartists@google.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] HID: sony: add support for more instruments
Date: Thu, 9 Apr 2026 00:12:22 +0200	[thread overview]
Message-ID: <cb0617fb-76b0-4241-8fba-982a5ffa4525@mailbox.org> (raw)
In-Reply-To: <o488s484-r1os-6736-o800-7on55687757s@xreary.bet>

Hello,

Yes I do apologize, and I'll be mindful of either doing a series, mark 
dependencies clearly or do a pull request.

I didn't expect to be sending this many patches at all in the first 
place, but one minor annoyance of the code bothers me one day and then 
another day someone else mentions that e.g a device name is incorrect, 
so that kinda led to this chaos.

Apologies and I'll try preventing it in the future, and thanks for the 
advice,
Rosalie

On 4/9/26 00:08, Jiri Kosina wrote:
> On Thu, 9 Apr 2026, Rosalie wrote:
> 
>> Hello,
>>
>> I've sent 'HID: sony: fix incorrect Squier name and remove non-existent
>> device', though I will mention you didn't apply 'HID: quirks: update hid-sony
>> supported devices' cleanly because it duplicated the vendor and device ID
>> defines in hid-ids.h for the Wii instruments so it will not compile, I'd
>> advise you apply the patches in the following order to prevent issues:
>>
>> 1) v1 of 'HID: sony: add support for more instruments'
>> 2) 'HID: sony: fix incorrect Squier name and remove non-existent device'
>> 3) v2 of 'HID: quirks: update hid-sony supported devices' but without changing
>> hid-ids.h
>> 4) v2 of 'HID: sony: fix style issues' (if you want this patch to be included
>> that is)
>>
>> alternatively you could also do:
>>
>> 1) v2 of 'HID: sony: add support for more instruments'
>> 2) v2 of 'HID: quirks: update hid-sony supported devices'
>> 3) v2 of 'HID: sony: fix style issues'
>>
>> I hope this doesn't cause too much hassle,
> 
> Thanks, I will look into it. But going forward, you really should either
> send this as series, or clearly mark the dependencies. Sending it as a
> followup fix in the same thread also works.
> 
> Or, even better, send a pull request against a git branch if the
> interdependencies are tricky.
> 
> Imagine you're getting higher tens of patches a day (including e.g. quite
> often v1->v5 within a timeframe of a few hours), and you are somehow
> magically expected to untangle all this.
> 
> Thanks,
> 


  reply	other threads:[~2026-04-08 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 19:46 [PATCH v2] HID: sony: add support for more instruments Rosalie Wanders
2026-04-08 20:41 ` Jiri Kosina
2026-04-08 22:01   ` Rosalie
2026-04-08 22:08     ` Jiri Kosina
2026-04-08 22:12       ` Rosalie [this message]
2026-04-08 22:19         ` Jiri Kosina
2026-04-08 22:41           ` Rosalie
2026-04-08 22:44             ` 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=cb0617fb-76b0-4241-8fba-982a5ffa4525@mailbox.org \
    --to=rosalie@mailbox.org \
    --cc=appsforartists@google.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanjay.govind9@gmail.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