public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: George Spelvin <linux@horizon.com>
Cc: udovdh@xs4all.nl, linux-kernel@vger.kernel.org, LinuxPPS@ml.enneenne.com
Subject: Re: [LinuxPPS] LinuxPPS kernel interface
Date: Mon, 9 Feb 2009 11:17:30 +0100	[thread overview]
Message-ID: <20090209101730.GM7975@enneenne.com> (raw)
In-Reply-To: <20090208060938.25184.qmail@science.horizon.com>

On Sun, Feb 08, 2009 at 01:09:38AM -0500, George Spelvin wrote:
> Udo van den Heuvel <udovdh@xs4all.nl> wrote:
> > Interesting ideas, thanks for the input.
> >
> > I think I must mention  that we also must strive for kernel inclusion.
> > Kernel inclusion will broaden our exposure.
> > This means we have to get rid of the issues blocking inclusion.
> > (see a query like http://marc.info/?l=linux-kernel&w=2&r=1&s=pps&q=b for 
> > related posts)
> >
> > What do you think?
> 
> I agree, that's the goal.  But it's also important to get the
> interface right, preferably before publishing it to world+dog.
> 
> And then there are little things like the fact that an important header
> file like timepps.h probably shouldn't live in Documentation/pps...
> 
> For example, here's a patch, on top of the previous series, that
> gets rid of the timeout argument to PPS_FETCH:

Please, note that such file is _not_ into kernel proposed patch.

First we should get inclusion of core code, then we can discuss about
userland interface and other related stuff.

Ciao,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti

      reply	other threads:[~2009-02-09 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9dd2f03a0810280213v42811184pb14d80f90529d1d5@mail.gmail.com>
     [not found] ` <20081028111414.19650.qmail@science.horizon.com>
     [not found]   ` <20081028144735.GC28518@tekkaman>
     [not found]     ` <20081028181335.29352.qmail@science.horizon.com>
     [not found]       ` <20081028181546.GM11339@tekkaman>
     [not found]         ` <20090206142231.22425.qmail@science.horizon.com>
     [not found]           ` <20090206143703.GC7975@enneenne.com>
     [not found]             ` <20090206144752.5195.qmail@science.horizon.com>
     [not found]               ` <20090206145553.GD7975@enneenne.com>
     [not found]                 ` <20090206145932.10638.qmail@science.horizon.com>
     [not found]                   ` <20090206152156.GE7975@enneenne.com>
     [not found]                     ` <20090206225326.14093.qmail@science.horizon.com>
2009-02-08  0:49                       ` LinuxPPS kernel interface George Spelvin
2009-02-08  1:56                         ` Lennart Sorensen
2009-02-08  4:00                           ` George Spelvin
2009-02-08 16:35                             ` Lennart Sorensen
     [not found]                         ` <498E712F.7080206@xs4all.nl>
2009-02-08  6:09                           ` [LinuxPPS] " George Spelvin
2009-02-09 10:17                             ` Rodolfo Giometti [this message]

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=20090209101730.GM7975@enneenne.com \
    --to=giometti@enneenne.com \
    --cc=LinuxPPS@ml.enneenne.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=udovdh@xs4all.nl \
    /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