From: Aditya Garg <gargaditya08@live.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"bentiss@kernel.org" <bentiss@kernel.org>,
Alex Henrie <alexhenrie24@gmail.com>,
"jose.exposito89@gmail.com" <jose.exposito89@gmail.com>,
"bruners@gmail.com" <bruners@gmail.com>,
"seobrien@chromium.org" <seobrien@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] HID: apple: Use common table for MacBook Pro fn mapping
Date: Wed, 5 Mar 2025 04:11:03 +0000 [thread overview]
Message-ID: <EE70DDCC-1868-4BBF-B37A-6449A0D25333@live.com> (raw)
In-Reply-To: <93E79E35-15B1-46BC-BA76-C54784351E6A@live.com>
> On 5 Mar 2025, at 9:03 AM, Aditya Garg <gargaditya08@live.com> wrote:
>
> Hi Jiri
>>
>> This patch is corrupt -- the context lines are missing the leading space.
>> For some reason, it's only the 1/4 which is corrupted, the rest is fine.
>>
>> Can you please look into this and resubmit?
>
>
> I sent another patchset yesterday since common tables were becoming confusing for people, so dropped those patches.
>
> Please review this patchset:
>
> https://lore.kernel.org/linux-input/F4DF8D56-7095-43AE-A788-F10B8CE477B0@live.com/
You may also want to review this small patch, which is related:
https://lore.kernel.org/linux-input/4CBC715A-59C2-4815-8D90-62683850E176@live.com/T/#u
prev parent reply other threads:[~2025-03-05 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 10:05 Aditya Garg
2025-02-14 10:06 ` [PATCH v2 2/4] HID: apple: Use common table for Magic Keyboard aluminium and 2015 " Aditya Garg
2025-02-14 10:07 ` [PATCH v2 3/4] HID: apple: simplify logic for swapping only left sided option and command keys Aditya Garg
2025-02-14 10:08 ` [PATCH v2 4/4] HID: apple: use switch case to assign devices to their respective fn mapping Aditya Garg
2025-02-18 19:59 ` [PATCH v2 1/4] HID: apple: Use common table for MacBook Pro " Jiri Kosina
2025-02-18 20:08 ` Aditya Garg
2025-02-19 16:43 ` Aditya Garg
2025-03-04 20:23 ` Jiri Kosina
2025-03-05 3:33 ` Aditya Garg
2025-03-05 4:11 ` 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=EE70DDCC-1868-4BBF-B37A-6449A0D25333@live.com \
--to=gargaditya08@live.com \
--cc=alexhenrie24@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bentiss@kernel.org \
--cc=bruners@gmail.com \
--cc=jikos@kernel.org \
--cc=jose.exposito89@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seobrien@chromium.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®