On Sun, Oct 06, 2013 at 07:40:52PM +0200, Nicolas Joly wrote:
>
> Checking syscalls.master mknodat(2) definition needs to be updated for
> correct device argument type. It currently use uint32_t where it
> should be dev_t ...
Here is the corresponding patch, for review. It changes the syscall
dev
On Sun, Oct 06, 2013 at 10:51:36PM +0200, Nicolas Joly wrote:
>
> It needs the PAD, syscalls files generation fails without it
> (sysalign=1).
>
> /bin/sh makesyscalls.sh syscalls.conf syscalls.master
> syscalls.master: line 905: unexpected dev (expected )
> line is:
> 460 STD RUMP{
On Sun, Oct 06, 2013 at 04:59:19PM -0400, Christos Zoulas wrote:
> On Oct 6, 10:51pm, nj...@pasteur.fr (Nicolas Joly) wrote:
> -- Subject: Re: mknodat(2) device argument type change
[...]
> | It needs the PAD, syscalls files generation fails without it
> | (sysalign=1).
>
On Oct 6, 10:51pm, nj...@pasteur.fr (Nicolas Joly) wrote:
-- Subject: Re: mknodat(2) device argument type change
| On Sun, Oct 06, 2013 at 05:56:58PM +, Christos Zoulas wrote:
| > In article <20131006174052.ga27...@lynche.sis.pasteur.fr>,
| > Nicolas Joly wrote:
|
On Sun, Oct 06, 2013 at 05:56:58PM +, Christos Zoulas wrote:
> In article <20131006174052.ga27...@lynche.sis.pasteur.fr>,
> Nicolas Joly wrote:
> >
> >Hi,
> >
> >Checking syscalls.master mknodat(2) definition needs to be updated for
> >correct device argument type. It currently use uint32_t w
In article <20131006174052.ga27...@lynche.sis.pasteur.fr>,
Nicolas Joly wrote:
>
>Hi,
>
>Checking syscalls.master mknodat(2) definition needs to be updated for
>correct device argument type. It currently use uint32_t where it
>should be dev_t ...
>
>460 STD RUMP { int|sys||mknodat(int
Hi,
Checking syscalls.master mknodat(2) definition needs to be updated for
correct device argument type. It currently use uint32_t where it
should be dev_t ...
460 STD RUMP { int|sys||mknodat(int fd, const char *path, \
mode_t mode, uint32_t dev); }
Simply
