From: David Howells <dhowells@redhat.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: dhowells@redhat.com, James Hogan <james@albanarts.com>,
torvalds@osdl.org, arnd@arndb.de, hpa@zytor.com,
alan@lxorguk.ukuu.org.uk, fengguang.wu@intel.com,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)
Date: Thu, 08 Nov 2012 12:38:31 +0000 [thread overview]
Message-ID: <1171.1352378311@warthog.procyon.org.uk> (raw)
In-Reply-To: <509251CA.8050008@synopsys.com>
Vineet Gupta <Vineet.Gupta1@synopsys.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
next prev parent reply other threads:[~2012-11-08 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 18:36 [GIT PULL] User API Disintegrate: Preparatory patches David Howells
2012-10-04 17:12 ` Geert Uytterhoeven
2012-10-04 17:36 ` David Howells
2012-10-17 8:42 ` James Hogan
2012-10-22 11:50 ` James Hogan
2012-11-01 10:41 ` UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches) Vineet Gupta
2012-11-08 12:38 ` David Howells [this message]
2012-11-08 14:36 ` David Howells
2012-11-08 15:07 ` David Howells
2012-11-08 18:21 ` Vineet Gupta
2012-11-08 23:19 ` David Howells
2012-11-12 10:57 ` [arc-linux-dev] " Vineet Gupta
2012-11-12 13:14 ` David Howells
2012-11-14 13:01 ` James Hogan
2012-11-14 16:28 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1171.1352378311@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=james@albanarts.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).