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: <1171.1352378311@warthog.procyon.org.uk>
Date:	Thu, 08 Nov 2012 12:38:31 +0000
From:	David Howells <dhowells@...hat.com>
To:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc:	dhowells@...hat.com, James Hogan <james@...anarts.com>,
	torvalds@...l.org, arnd@...db.de, hpa@...or.com,
	alan@...rguk.ukuu.org.uk, fengguang.wu@...el.com,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

Vineet Gupta <Vineet.Gupta1@...opsys.com> wrote:

> I'm planning to submit ARC Linux kernel port (from Synopsys) for review
> on lkml and arch mailing lists. I already have a a 3.7-rc3 based kernel
> (modulo the arch UAPI split). What would be the best way to get the UAPI
> split done.

Do you want the headers to be split in the patches that add them, or would you
be happy with one patch stacked on the end to do the whole lot?  The last is
easiest for me to do.

However, I could 'uncommit' your patches using stgit, do the headers
individually and recommit them if you'd prefer.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ