public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel@vger.kernel.org, linuxpps@ml.enneenne.com
Subject: Re: [RFC] PPS: Implementing LinuxPPS API with new syscalls
Date: Wed, 6 Jun 2007 13:29:34 -0700	[thread overview]
Message-ID: <20070606132934.18606a17.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070605072501.GA15273@enneenne.com>

On Tue, 5 Jun 2007 09:25:01 +0200 Rodolfo Giometti <giometti@enneenne.com> wrote:

> Hello,
> 
> after a little studing on new generic netlink interface and some
> letters with Andrew Morton I decided to drop using the netlink API at
> all and start using new specific syscalls.
> 
> Looking at current LinuxPPS API and at RFC2783 I think we need the
> following syscalls:
> 
>    asmlinkage long sys_time_pps_find(int cmd, int __user *source,
>                                           char __user *name, int namelen,
>                                           char __user *path, int pathlen);
>    asmlinkage long sys_time_pps_getparams(int source,
>                                           struct pps_params __user *params);
>    asmlinkage long sys_time_pps_setparams(int source,
>                                           const struct pps_params __user *params);
>    asmlinkage long sys_time_pps_getcap(int source, int __user *mode);
>    asmlinkage long sys_time_pps_fetch(int source, const int tsformat,
>                                           struct pps_info __user *info,
>                                           const struct timespec __user *timeout);

Could we please also see those structs which are being passed in and out of
the kernel?  It's a bit hard to understand the proposed interface without
that information.

They don't have to be 100% accurate - just an overview.

Hopefully each member of these structs has a little comment explaining what
it is, too...

Thanks.



  reply	other threads:[~2007-06-06 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05  7:25 [RFC] PPS: Implementing LinuxPPS API with new syscalls Rodolfo Giometti
2007-06-06 20:29 ` Andrew Morton [this message]
2007-06-06 21:24   ` Rodolfo Giometti
2007-06-07 10:14     ` Rodolfo Giometti

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=20070606132934.18606a17.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=giometti@enneenne.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxpps@ml.enneenne.com \
    /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