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] [day] [month] [year] [list]

Message-ID: <20090923085512.GC3737@elte.hu>
Date:	Wed, 23 Sep 2009 10:55:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
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

* Andrew Morton <akpm@...ux-foundation.org> wrote:

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

Mass mailings of this order of magnitude are more common now and vger 
ought to cope. It would be sad to skip the useful stuff while keeping 
all the noise ;-)

At least as far as i'm concerned i grep for a commit's title and reply 
to the last relevant mail in the thread that comes up on lkml. That kind 
of activity would be sufficiently helped by a summary mail Cc:-ed to 
lkml. (And there's rumors that there's a wonderful new tool for that, 
written by a git - so i heard.)

Alternatively (or in addition to that) the mm commits list could Cc: 
over to lkml.

( It might even use LKML-Reference tag for that purpose - that way 
  patches which are queued up (or updated) in -mm will show up on lkml 
  gradually and in relevant threads. Highly useful in practice - not 
  only does it make the flow of patches more transparent on lkml, it 
  also links the commit back to the discussion and allows others to 
  chime in later in the discussion (even if they were not Cc:-ed and are 
  hence outside the usual scope of mm-commits). Dunno whether you 
  consider it worth it to update the mm-commits scripts to that end. 
  Since you pick patches from emails it seems a perfect match to me. 
  YMMV. )

And if that is done then git-commits-head@...r.kernel.org could Cc: back 
to lkml if a LKML-Reference tag is present, and the 'hits upstream' 
notification would thus thread back to the original discussion as well.

All in the name of eternal laziness.

> 16af5bb doesn't exist btw - you want e258b80e691f1f3ae83a60aa80eaf7322bd55ec4.

Yeah, you are right, i meant e258b80e (correctly mentioned in the 
changelog).

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