Hi Firoz,
On Thu, Jan 3, 2019 at 12:55 PM Firoz Khan wrote:
> On Thu, 3 Jan 2019 at 17:04, Firoz Khan wrote:
> > > +fileguard=_UAPI_ASM_`basename "$out" | sed \
> >
> > Currently, all but MIPS have the architecture name included in
> > the file guard. Shouldn't that be retained?
>
> I was plann
Hi Geert,
On Thu, 3 Jan 2019 at 17:04, Firoz Khan wrote:
> > +fileguard=_UAPI_ASM_`basename "$out" | sed \
>
> Currently, all but MIPS have the architecture name included in
> the file guard. Shouldn't that be retained?
I was planning to do something similar to this:
-fileguard=_UAPI_ASM_`basen
++ adding more folks I closely worked with :)
On Wed, 2 Jan 2019 at 19:59, Firoz Khan wrote:
>
> System call table generation support is provided for
> alpha, ia64, m68k, microblaze, mips, parisc, powerpc,
> sh, sparc and xtensa architectures. The implementat-
> ions are almost similar across al
Hi Firoz,
Thanks for your patch!
On Wed, Jan 2, 2019 at 3:30 PM Firoz Khan wrote:
> System call table generation support is provided for
> alpha, ia64, m68k, microblaze, mips, parisc, powerpc,
> sh, sparc and xtensa architectures. The implementat-
> ions are almost similar across all the above a
4 matches
Mail list logo