From: Aditya Garg <gargaditya08@live.com>
To: Jiri Kosina <jikos@kernel.org>,
"jkosina@suse.com" <jkosina@suse.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"bentiss@kernel.org" <bentiss@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 0/2] HID: apple: improvements for code readability
Date: Fri, 7 Mar 2025 12:02:36 +0000 [thread overview]
Message-ID: <DA80C1BF-4E90-4F1A-BE83-BFE25D5415A4@live.com> (raw)
In-Reply-To: <F4DF8D56-7095-43AE-A788-F10B8CE477B0@live.com>
> On 4 Mar 2025, at 2:42 PM, Aditya Garg <gargaditya08@live.com> wrote:
>
> Hi
>
> This small patch series aims to improve the code readability in hid-apple.
>
> The first patch moves the backlight report structs, that were incorrectly
> placed between the translation tables, to other related backlight structs.
>
> The second patch makes use of switch case statements for the ever
> increasing lengthy device table for fn translation.
>
> Aditya Garg (2):
> HID: apple: move backlight report structs alongwith other backlight
> structs
> HID: apple: use switch case to set fn translation table
>
> drivers/hid/hid-apple.c | 100 ++++++++++++++++++++++------------------
> 1 file changed, 54 insertions(+), 46 deletions(-)
>
> --
> 2.43.0
>
A v2 with more patches has been sent here:
https://lore.kernel.org/linux-input/A4FBEA54-C7BA-4864-9C4E-E41933D81FB0@live.com/T/#t
There were conflicting patches sent upstream by another person, so its best to combine them in one series, making things easier for both of us.
prev parent reply other threads:[~2025-03-07 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 9:12 Aditya Garg
2025-03-04 9:13 ` [PATCH 1/2] HID: apple: move backlight report structs to other backlight structs Aditya Garg
2025-03-04 9:14 ` [PATCH 2/2] HID: apple: use switch case to set fn translation table Aditya Garg
2025-03-07 12:02 ` Aditya Garg [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=DA80C1BF-4E90-4F1A-BE83-BFE25D5415A4@live.com \
--to=gargaditya08@live.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=jkosina@suse.com \
--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
all inboxes | Powered by JetHome®