linux-kernel - Re: Process to push changes to include/linux/types.h

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]

Message-Id: <20101014150144.3d895940.akpm@linux-foundation.org>
Date:	Thu, 14 Oct 2010 15:01:44 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jan Engelhardt <jengelh@...ozas.de>
Cc:	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, agruen@...e.de, davem@...emloft.net,
	andi@...stfloor.org
Subject: Re: Process to push changes to include/linux/types.h

On Thu, 14 Oct 2010 23:50:34 +0200 (CEST)
Jan Engelhardt <jengelh@...ozas.de> wrote:

> 
> On Thursday 2010-10-14 23:37, Andrew Morton wrote:
> >> >The usual approach here is someone sends it to me and I send it to
> >> >Linus ;)
> >> 
> >> We tinkered on types.h before, with the change originating in the Netfilter
> >> subtree, and nobody, not even Dave, complained.
> >
> >It doesn't matter much at all what tree a change goes through.  What
> >matters more is that the appropriate people know about and see the
> >change.
> >
> >For example, I never even knew that aligned_u64 and friends existed (it
> >got secretly merged via the netfilter tree, apparently).
> 
> I would be interested in knowing whether you - in whichever subsystems
> you happen to be active - would even need aligned_u64. Right now,
> the only users seem to be PPP and scsi_tgt besides Netfilter.
> 

Stranger things have happened.

include/linux/net_dropmon.h:net_dm_config_entry can perhaps be
converted btw.

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