linux-kernel - Re: [PATCH 22/29] Disintegrate asm/system.h for S390

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: <14404.1331595606@redhat.com>
Date:	Mon, 12 Mar 2012 23:40:06 +0000
From:	David Howells <dhowells@...hat.com>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	dhowells@...hat.com, paul.gortmaker@...driver.com, hpa@...or.com,
	torvalds@...ux-foundation.org, sfr@...b.auug.org.au,
	mingo@...hat.com, arnd@...db.de, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH 22/29] Disintegrate asm/system.h for S390

Martin Schwidefsky <schwidefsky@...ibm.com> wrote:

> This hunk will conflict with "[PATCH] rework smp code" in the linux-next
> tree. The sigp.h header is disintegrated as well..
> But except for this little hiccup I like the idea to split system.h,
> makes a lot of sense.

I've just posted a new version of my patchset that reverses the order of the
patches to put the arch-specific bits first.  Each arch-specific bit is a
stand-alone reduction of that asm/system.h to just a bunch of #includes which
is deleted by the final patch (except where asm-generic/system.h is involved).

As these are independent, it would, for example, be possible to just take the
s390 one into your tree and merge it with your changes.

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