Re: New getsockopt2() syscall

Commit it then? christos > On Jul 30, 2018, at 3:42 AM, Robert Swindells wrote: > > > chris...@zoulas.com (Christos Zoulas) wrote: >> On Jun 24, 11:18pm, r...@fdy2.co.uk (Robert Swindells) wrote: >> -- Subject: Re: New getsockopt2() syscall >> &g

Re: New getsockopt2() syscall

chris...@zoulas.com (Christos Zoulas) wrote: >On Jun 24, 11:18pm, r...@fdy2.co.uk (Robert Swindells) wrote: >-- Subject: Re: New getsockopt2() syscall > >How about merging them thusly? > >christos > >Index: uipc_syscalls.c >=

Re: New getsockopt2() syscall

On Jun 24, 11:18pm, r...@fdy2.co.uk (Robert Swindells) wrote: -- Subject: Re: New getsockopt2() syscall How about merging them thusly? christos Index: uipc_syscalls.c === RCS file: /cvsroot/src/sys/kern/uipc_syscalls.c,v retrieving

Re: New getsockopt2() syscall

chris...@zoulas.com (Christos Zoulas) wrote: >On Jun 24, 7:47pm, r...@fdy2.co.uk (Robert Swindells) wrote: >-- Subject: Re: New getsockopt2() syscall > >| What about the syscall implementation itself ? > >Where is the code for that? Here: <http://mail-index.netbsd.org

Re: New getsockopt2() syscall

On Jun 24, 7:47pm, r...@fdy2.co.uk (Robert Swindells) wrote: -- Subject: Re: New getsockopt2() syscall | What about the syscall implementation itself ? Where is the code for that? christos

Re: New getsockopt2() syscall

chris...@astron.com (Christos Zoulas) wrote: >In article , >Robert Swindells wrote: >> >>chris...@zoulas.com (Christos Zoulas) wrote: >>>On Jun 9, 2:20pm, r...@fdy2.co.uk (Robert Swindells) wrote: >>>-- Subject: Re: New getsockopt2() syscall >>>

Re: New getsockopt2() syscall

In article , Robert Swindells wrote: > >chris...@zoulas.com (Christos Zoulas) wrote: >>On Jun 9, 2:20pm, r...@fdy2.co.uk (Robert Swindells) wrote: >>-- Subject: Re: New getsockopt2() syscall >> >>| What is the best way to provide it for review, diffs or the compl

Re: New getsockopt2() syscall

Martin Husemann wrote: >On Sat, Jun 09, 2018 at 10:22:06AM +0200, Kamil Rytarowski wrote: >> Can we reuse unused old syscall numbers? > >Reuse in general not (that would break any possible compat for that). >But there are some unused numbers like 193 and 267-269. I have switched to using 193.

Re: New getsockopt2() syscall

chris...@zoulas.com (Christos Zoulas) wrote: >On Jun 9, 2:20pm, r...@fdy2.co.uk (Robert Swindells) wrote: >-- Subject: Re: New getsockopt2() syscall > >| What is the best way to provide it for review, diffs or the complete >| page ? > >Either way. I think that the complet

Re: New getsockopt2() syscall

On 09.06.2018 16:05, Martin Husemann wrote: > On Sat, Jun 09, 2018 at 10:22:06AM +0200, Kamil Rytarowski wrote: >> Can we reuse unused old syscall numbers? > > Reuse in general not (that would break any possible compat for that). > But there are some unused numbers like 193 and 267-269. > > Marti

Re: New getsockopt2() syscall

Kamil Rytarowski wrote: >On 08.06.2018 23:18, Robert Swindells wrote: >> >> Are there any objections to the code for a getsockopt2() syscall >> in: >> >> >> > >Can we reuse unused old syscall numbers? Why ? We are not going t

Re: New getsockopt2() syscall

chris...@astron.com (Christos Zoulas) wrote: >In article , >Robert Swindells wrote: >> >>Are there any objections to the code for a getsockopt2() syscall >>in: >> >> > >Let's write the man page to see if it makes sense :-) What

Re: New getsockopt2() syscall

On Jun 9, 2:20pm, r...@fdy2.co.uk (Robert Swindells) wrote: -- Subject: Re: New getsockopt2() syscall | What is the best way to provide it for review, diffs or the complete | page ? Either way. I think that the complete man page is not too long (I just looked). christos

Re: New getsockopt2() syscall

On Sat, Jun 09, 2018 at 10:22:06AM +0200, Kamil Rytarowski wrote: > Can we reuse unused old syscall numbers? Reuse in general not (that would break any possible compat for that). But there are some unused numbers like 193 and 267-269. Martin

Re: New getsockopt2() syscall

On 08.06.2018 23:18, Robert Swindells wrote: > > Are there any objections to the code for a getsockopt2() syscall > in: > > > Can we reuse unused old syscall numbers? signature.asc Description: OpenPGP digital signature

Re: New getsockopt2() syscall

In article , Robert Swindells wrote: > >Are there any objections to the code for a getsockopt2() syscall >in: > > Let's write the man page to see if it makes sense :-) christos

New getsockopt2() syscall

Are there any objections to the code for a getsockopt2() syscall in: