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: <20080812220545.3541f1d4.akpm@linux-foundation.org>
Date:	Tue, 12 Aug 2008 22:05:45 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 22/22] byteorder: remove the old byteorder
 implementation

On Tue, 12 Aug 2008 17:27:17 -0700 Harvey Harrison <harvey.harrison@...il.com> wrote:

>  include/linux/byteorder/Kbuild          |    3 -
>  include/linux/byteorder/big_endian.h    |  108 ---------------
>  include/linux/byteorder/generic.h       |  173 ------------------------
>  include/linux/byteorder/little_endian.h |  108 ---------------
>  include/linux/byteorder/swab.h          |  222 -------------------------------
>  include/linux/byteorder/swabb.h         |  135 -------------------

akpm2:/usr/src/25> make headers_check
  CHK     include/linux/version.h
make[1]: `scripts/unifdef' is up to date.
/usr/src/devel/scripts/Makefile.headersinst:15: /usr/src/devel/include/linux/byteorder/Kbuild: No such file or directory
make[3]: *** No rule to make target `/usr/src/devel/include/linux/byteorder/Kbuild'.  Stop.

This is just a basic i386 allmodconfig :(  The largest risk from
these patches is build breakage, and it is quite obvious that they have
not had anything like adequate build coverage testing.

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