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: <m1d53k8dkx.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 07 Mar 2007 23:16:30 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	vgoyal@...ibm.com
Cc:	Sam Ravnborg <sam@...nborg.org>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Reloc Kernel List <fastboot@...ts.osdl.org>,
	akpm@...ux-foundation.org, ak@...e.de, hpa@...or.com,
	magnus.damm@...il.com, lwang@...hat.com, dzickus@...hat.com,
	pavel@...e.cz, rjw@...k.pl
Subject: Re: [PATCH 1/20] x86_64: Assembly safe page.h and pgtable.h

Vivek Goyal <vgoyal@...ibm.com> writes:

> Hi Sam,
>
> Thanks for the review. This makes sense to me. Move const.h into
> asm-generic and let everybody use it.
>
> This is more of a small cleanup issue and involves changing few header files
> in asm-sparc64 and make sure nothing is broken on sparc64. This patchset
> is already becoming big and complex. Is it ok if we let the patch 
> remain unmodified for now and once this gets in and settles down, I can
> post another patch to do above modification?

Actually unless there is a reason not to, we can probably move this
into include/linux instead of include/asm-generic.  I don't see anything
in that header file that is architecture specific in any way.  Except
that it happens to only be used in architecture specific code.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ