linux-kernel - [PATCH 0/3] Get defconfig to work with ARCH=um

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

Date:	Fri,  5 Jul 2013 02:33:14 +0530
From:	Ramkumar Ramachandra <artagnon@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] Get defconfig to work with ARCH=um

Hi,

  $ ARCH=um make defconfig
  $ ARCH=um make

does not work on 64-bit hosts, because the build-infrastructure is
hard-wired to pick a 32-bit defconfig when ARCH=um.  This series fixes
the problem.

[1/3] is somewhat unrelated to the series, and I happened to notice it
while reading.  12783aa07 (um: Switch to large mcmodel on x86_64,
2012-01-24) indicates that I did something stupid, but I don't know
what.

Thanks.

Ramkumar Ramachandra (3):
  arch/um/Makefile: remove dead code
  arch/um/configs: add defconfig for i386, x86_64
  arch/um: migrate to using defconfig in configs/

 arch/um/Kconfig.common                          |   5 -
 arch/um/Makefile                                |  20 +-
 arch/um/{defconfig => configs/i386_defconfig}   | 209 +++++++++++++-------
 arch/um/{defconfig => configs/x86_64_defconfig} | 250 +++++++++++++++---------
 arch/x86/um/Kconfig                             |   5 +
 5 files changed, 306 insertions(+), 183 deletions(-)
 copy arch/um/{defconfig => configs/i386_defconfig} (86%)
 rename arch/um/{defconfig => configs/x86_64_defconfig} (83%)

-- 
1.8.3.1.643.gebeea52.dirty

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