Re: [arc-linux-dev] Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-14 Thread David Howells
James Hogan wrote: > The disintegration scripts strip out the #ifdef __KERNEL__ from the > headers in both uapi/ and the old directories. However there are still a > bunch of unexported headers through the tree which have #ifdef > __KERNEL__ in them, usually guarding the entire file (just grep >

Re: [arc-linux-dev] Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-14 Thread James Hogan
Hi David, The disintegration scripts strip out the #ifdef __KERNEL__ from the headers in both uapi/ and the old directories. However there are still a bunch of unexported headers through the tree which have #ifdef __KERNEL__ in them, usually guarding the entire file (just grep __KERNEL__ in arch/)

Re: [arc-linux-dev] Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-12 Thread David Howells
Vineet Gupta wrote: > >> Per you email from last week, When I ran the disintergrate-one.pl script > >> myself I saw a whole bunch of empty UAPI files being generated with > >> references in orig header. I'm not sure what I'm doing wrong. > > Can you give an example of such a header? > > tlb.h -

Re: [arc-linux-dev] Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-12 Thread Vineet Gupta
On Friday 09 November 2012 04:49 AM, David Howells wrote: > Vineet Gupta wrote: > >> While I'd done some of the prep work in my code such as splitting __KERNEL__ >> && __ASSEMBLY__ into two separate lines, majority of orig headers didn't >> have #ifdef __KERNEL__ guard despite the code not being m

Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-08 Thread David Howells
Vineet Gupta wrote: > While I'd done some of the prep work in my code such as splitting __KERNEL__ > && __ASSEMBLY__ into two separate lines, majority of orig headers didn't > have #ifdef __KERNEL__ guard despite the code not being meant for user-space > ABI. Is that fundamental to UAPI split scr

RE: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-08 Thread Vineet Gupta
> Vineet Gupta 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. >> >> Can you point me to the late

Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-08 Thread David Howells
Vineet Gupta 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. > > Can you point me to the latest scri

Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-08 Thread David Howells
Vineet Gupta wrote: > git://github.com/organizations/foss-for-synopsys-dwc-arc-processors/linux.git That seems to be wrong. I think you mean: git://github.com/foss-for-synopsys-dwc-arc-processors/linux.git David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel

Re: UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-08 Thread David Howells
Vineet Gupta 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

UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches)

2012-11-01 Thread Vineet Gupta
On Monday 22 October 2012 05:20 PM, James Hogan wrote: > On 17 October 2012 09:42, James Hogan wrote: >> On 2 October 2012 19:36, David Howells wrote: >>> The patches herein prepare for the extraction of the Userspace API bits from >>> the various header files named in the Kbuild files. >>> >>> [

Re: [GIT PULL] User API Disintegrate: Preparatory patches

2012-10-22 Thread James Hogan
On 17 October 2012 09:42, James Hogan wrote: > On 2 October 2012 19:36, David Howells 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 he

Re: [GIT PULL] User API Disintegrate: Preparatory patches

2012-10-17 Thread James Hogan
On 2 October 2012 19:36, David Howells 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 normall

Re: [GIT PULL] User API Disintegrate: Preparatory patches

2012-10-04 Thread David Howells
Geert Uytterhoeven wrote: > > include/linux/libfdt.h | 4 +- > > So what happened here? > > -#include "../../scripts/dtc/libfdt/fdt.h" > -#include "../../scripts/dtc/libfdt/libfdt.h" > +#include <> > +#include <> I didn't expect 'system' header files to be outside o

Re: [GIT PULL] User API Disintegrate: Preparatory patches

2012-10-04 Thread Geert Uytterhoeven
On Tue, Oct 2, 2012 at 8:36 PM, David Howells wrote: > include/linux/libfdt.h | 4 +- So what happened here? -#include "../../scripts/dtc/libfdt/fdt.h" -#include "../../scripts/dtc/libfdt/libfdt.h" +#include <> +#include <> Woops... http://kisskb.ellerman.id.au/kiss

[GIT PULL] User API Disintegrate: Preparatory patches

2012-10-02 Thread David Howells
Hi Linus, Could you pull this tree please? 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 v