linux-kernel - Re: [origin tree build failure] [PATCH] input: Fix build failures caused by Kconfig Winbond WPCD376I Consumer IR hardware driver Kconfig entry

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]

Message-Id: <20090923003918.505db5b4.akpm@linux-foundation.org>
Date:	Wed, 23 Sep 2009 00:39:18 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>, david@...deman.nu,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [origin tree build failure] [PATCH] input: Fix build failures
 caused by Kconfig Winbond WPCD376I Consumer IR hardware driver Kconfig
 entry

On Wed, 23 Sep 2009 09:24:44 +0200 Ingo Molnar <mingo@...e.hu> wrote:

> ( ob-sidenote: Andrew, i did not find the patch for commit 16af5bb on 
>   lkml and it's now upstream. It would be highly useful if you Cc:-ed 
>   lkml with submitted patches like all maintainers do, so that patterns 
>   can be grepped for and discussions can be continued quickly instead of 
>   created anew. It would also significantly increase the S/N ratio of 
>   lkml. Thanks! )

I did that a couple of times a few years back and vger had a heart
attack.  I could cc the lower-subscriber-count mm-commits but that
wouldn't help much.

16af5bb doesn't exist btw - you want e258b80e691f1f3ae83a60aa80eaf7322bd55ec4.
--
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/