From: Carson <crange76@gmail.com>
To: Milas Robin <milas.robin@live.fr>
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
milas.robin@live.fr
Subject: Re: gamecube adapter driver
Date: Tue, 07 May 2024 14:04:30 -0400 [thread overview]
Message-ID: <2693037.vuYhMxLoTh@mythra> (raw)
In-Reply-To: <PA4P189MB146957B28CBD2F35D6479C47FA1C2@PA4P189MB1469.EURP189.PROD.OUTLOOK.COM>
On Monday, May 6, 2024 3:32:20 PM EDT Milas Robin wrote:
> Hi,
>
> I don't think so, I didn't received any reply so I guess it is not ?
> If you have some time to review the code I would be grateful.
> As I said in the cover letter (which didn't linked correctly), this is
> my first kernel module so there might be some basic architecture notably
> on race conditions.
>
> Also due to the way I've implemented it, if it is build as a module
> it lose priority over the usb-hid generic driver as the device report
> supporting hid it.
>
> One other thing which might make the code heavier to read is properly
> detecting if the controller really support rumbles, I actually ignore the
> bit signalling it cause I don't know if the adapter could change it without
> unplugging the controller which might lead to have to recreate the device
> to switch it's rumbling capability
>
> The patch seems to have no conflict with the current input/next branch.
> If you need a branch I've uploaded it on https://github.com/Hinara/linux.git
> The branch is called ngc.
I've built the kernel but it won't boot, its likely a issue with my config but
could you rebase the patch to a newer kernel. Also I believe we are not
contacting the correct person for a merge.
https://github.com/torvalds/linux/blob/master/MAINTAINERS#L15595
next prev parent reply other threads:[~2024-05-07 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 16:19 gamecube adapter driver Carson
2024-05-06 19:32 ` Milas Robin
2024-05-07 18:04 ` Carson [this message]
2024-05-07 19:04 ` Milas Robin
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=2693037.vuYhMxLoTh@mythra \
--to=crange76@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=milas.robin@live.fr \
/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