From: Jeff Mitchell <jeff@jefferai.org>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, jvdillon@gmail.com,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Subject: Re: [PATCH] This adds support for keyboards on mid-2011 MacBook Airs
Date: Thu, 06 Oct 2011 10:56:00 -0400 [thread overview]
Message-ID: <4E8DC180.6060300@jefferai.org> (raw)
In-Reply-To: <20111005174347.GA28287@polaris.bitmath.org>
On 10/05/2011 01:43 PM, Henrik Rydberg wrote:
> On Wed, Oct 05, 2011 at 07:28:31PM +0200, Jiri Kosina wrote:
>> On Wed, 5 Oct 2011, Henrik Rydberg wrote:
>>
>>>> To clear up an earlier point: AFAIK the new MBAs have the same keyboard
>>>> layout as normal MacBooks and hence uses the same table. An earlier
>>>> patch that was floating around added another table for the new MBAs but
>>>> if you looked at the mappings it was the exact same table as the normal
>>>> MacBook one.
>>>
>>> I see. The current tree actually contains two identical tables. Yikes.
>>> Using your patch would have prevented this, but it might be too late
>>> now. If so, the (untested) patch below might fix things up. Does it
>>> still work for you?
I believe that that patch should remove the duplication without any
problem, so everything should still work so long as the other bits are
still there (adding the wellspring6/6a entries to the other files).
Thanks,
Jeff
prev parent reply other threads:[~2011-10-06 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 22:35 [PATCH] This adds support for keyboards on mid-2011 MacBook Airs Jeff Mitchell
2011-10-05 9:07 ` Henrik Rydberg
2011-10-05 9:04 ` Jiri Kosina
2011-10-05 9:48 ` Henrik Rydberg
2011-10-05 10:13 ` Jiri Kosina
2011-10-05 14:16 ` Jeff Mitchell
2011-10-05 17:28 ` Henrik Rydberg
2011-10-05 17:28 ` Jiri Kosina
2011-10-05 17:43 ` Henrik Rydberg
2011-10-06 14:56 ` Jeff Mitchell [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=4E8DC180.6060300@jefferai.org \
--to=jeff@jefferai.org \
--cc=iwamatsu@nigauri.org \
--cc=jkosina@suse.cz \
--cc=jvdillon@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).