linux-kernel - Re: [git pull] Input updates for 2.6.26-rc6

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, 18 Jun 2008 11:58:20 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] Input updates for 2.6.26-rc6

On Tue, 17 Jun 2008, Dmitry Torokhov wrote:

> Hi Linus,
> 
> Please pull from:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
> or
> 	master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
> 
> to receive updates for the input subsystem. There will be a small
> conflict in drivers/usb/core/quirks.c, I hope this is OK because I don't
> like to have merges on my 'for-linus' branch except for the one done in
> merge window for the next release. This way one can clearly see what
> went in into a release after the initial merge.
> 
> Changelog:
> ---------
> 
> Jiri Kosina (2):
>       Input: i8042 - add Fujitsu-Siemens Amilo Pro V2030 to nomux table
>       Input: i8042 - retry failed CTR writes when resuming

Hi Dmitry,

how about my patch

	Input: i8042 - add Intel D845PESV to nopnp list

Not that it couldn't wait for next merge window, I just want to make sure 
that it doesn't get lost.

Thanks,

-- 
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/