linux-kernel - Re: [PATCH] hid: Complete support for the new unibody macbooks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Nov 2008 18:06:10 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:	Henrik Rydberg <rydberg@...omail.se>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hid: Complete support for the new unibody macbooks

On Wed, 19 Nov 2008, Dmitry Torokhov wrote:

> > Yes, I am aware of bcm5974 being dependent in HID driver not claiming 
> > the mouse interface on this hardware.
> > Dmitry, what are your plans with this bcm5974 patch? 2.6.28 or 2.6.29?
> 2.6.29 - the driver is in use so I did nto want to touch it after .28 
> merge window closed. 

I see. I have already pushed the bits that ignore the mouse interface on 
the hardware in question in HID code. But that should be perfectly fine, 
as as the HID driver can't do anything with that mouse anyway.

> Also I am moving to the west coast so swamped anyways but I hope I will 
> be somewhat settled after December 8th.
> Btw, if you see something that you think needs to go into .28 for
> input could please merge it for me? I also going to ask Linus to pull
> from my for-linus branch in the next couple of days.

Sure, no problem, I will keep an eye on incoming input patches before you 
are fully settled again, and if anything new urgent comes, I will merge it 
for .28.

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/