linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: David Howells <dhowells@redhat.com>
Cc: 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: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)
Date: Thu, 1 Nov 2012 16:11:14 +0530	[thread overview]
Message-ID: <509251CA.8050008@synopsys.com> (raw)
In-Reply-To: <CAAG0J9_LZ5Q1fNdcbSOyieesabkqcTMT0ueEDLXmemV2C_+F=g@mail.gmail.com>

On Monday 22 October 2012 05:20 PM, James Hogan wrote:
> On 17 October 2012 09:42, James Hogan <james@albanarts.com> wrote:
>> On 2 October 2012 19:36, David Howells <dhowells@redhat.com> wrote:
>>> The patches herein prepare for the extraction of the Userspace API bits from
>>> the various header files named in the Kbuild files.
>>>
>>> [IMPORTANT NOTE!  These patches may need regenerating if the header files
>>>  change too much.  This doesn't normally take very long to do as the
>>>  disintegration procedure is almost entirely scripted.]
>>
>> Hi David,
>>
>> Any chance you (or somebody else) can point me towards your latest
>> scripts for all this UAPI disintegration work? They don't seem to be
>> in the kernel tree, and the only scripts I can find are from 2011 so I
>> guess they're probably a bit out of date.
> 
> Ping... Please can you point me to the scripts you've been using David?
> 
> Thanks
> James Hogan
> 

Hi David,

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.

Can you point me to the latest scripts and the best way to use them (so
we have consistent automated split of headers). Otherwise if you like,
you could take a stab at it yourself via my tree at

git://github.com/organizations/foss-for-synopsys-dwc-arc-processors/linux.git
arc-3.7-rc3-newport

TIA,
-Vineet

  reply	other threads:[~2012-11-01 10:41 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     ` Vineet Gupta [this message]
2012-11-08 12:38     ` UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches) David Howells
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=509251CA.8050008@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --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).