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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 13 Jan 2009 13:49:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...radead.org>,
	Sam Ravnborg <sam@...nborg.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PULL -tip] fixed few make headers_check warnings


* Jaswinder Singh Rajput <jaswinder@...radead.org> wrote:

> Hello Ingo,
> 
> Please pull these patches. Earlier I also floated these patches so that 
> I can get some feedback.

Sam, Andrew, David, what's your workflow preference for these bits?

While they are oneliners and i could create a separate branch for these 
and pull Jaswinder's tree (and do build coverage to make sure there's no 
surprised on any arch), it's really up to the maintainers of these files 
to decide on the workflow.

I'd lean towards doing this via the individual maintainers and/or -mm, but 
no strong feelings ...

Even if it's done via a separate tree at minimum it needs the acks from 
the affected maintainers.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ