From: Stuart <stuart.a.hayhurst@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Jiri Kosina <jikos@kernel.org>
Subject: Re: HID: corsair-void: Add Corsair Void headset family driver
Date: Mon, 19 Aug 2024 18:16:44 +0100 [thread overview]
Message-ID: <CALTg27n965pGk4UVLOWKRe1MDr0=Y870k1zVC3LP9b9Q7q9djg@mail.gmail.com> (raw)
In-Reply-To: <e0ccc03a-7479-4243-bd12-4d77b47308f4@web.de>
> How will applications of macro variants evolve further?
Sorry to get you to clarify again, but I'm not sure what you're asking.
Stuart
On Mon, Aug 19, 2024 at 6:53 AM Markus Elfring <Markus.Elfring@web.de> wrote:
>
> >> How do you think about to distinguish properties any further for available
> >> device attributes?
> >> https://elixir.bootlin.com/linux/v6.11-rc3/source/Documentation/driver-api/driver-model/device.rst#L38
> >
> > Sorry I'm not sure I follow you're saying
>
> I became curious about system fine-tuning possibilities.
>
>
> …
> >> * Can the macro “DEVICE_ATTR_RO” be applied?
> >
> > Done, also applied DEVICE_ATTR_WO
> …
>
>
> How will applications of macro variants evolve further?
>
> Regards,
> Markus
prev parent reply other threads:[~2024-08-19 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 15:38 [PATCH] HID: corsair-void: Add Corsair Void headset family driver Stuart Hayhurst
2024-08-15 4:19 ` kernel test robot
2024-08-15 7:50 ` Markus Elfring
2024-08-16 0:57 ` Stuart
2024-08-16 14:49 ` kernel test robot
2024-08-18 13:12 ` Markus Elfring
2024-08-18 23:17 ` Stuart
2024-08-19 5:53 ` Markus Elfring
2024-08-19 17:16 ` Stuart [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='CALTg27n965pGk4UVLOWKRe1MDr0=Y870k1zVC3LP9b9Q7q9djg@mail.gmail.com' \
--to=stuart.a.hayhurst@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).