All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] LinuxPPS - PPS support for Linux
Date: Tue, 23 Oct 2007 22:35:48 +0200	[thread overview]
Message-ID: <20071023203547.GO9748@enneenne.com> (raw)
In-Reply-To: <20071023201750.GE7793@redhat.com>

On Tue, Oct 23, 2007 at 04:17:50PM -0400, Dave Jones wrote:
> On Tue, Oct 23, 2007 at 08:04:18PM +0200, Rodolfo Giometti wrote:
> 
> Hi Rodolfo,

Hi! :)

>  > here my last patch for PPS support.
>  > 
>  > Please, let me know if I have something to do for kernel inclusion.
> 
> Thanks for trying to get this merged, we've had a few users asking
> us to support this in the Fedora kernel.

This sounds good! ;)

> >From a quick look through, it doesn't look too bad.
> A couple of obvious things that jumped out..
> 
> * The example program in the Documentation dir.
>   There was some discussion recently about moving away 
>   from doing this, and instead moving code to the samples/ dir
>   (or including it in util-linux instead if applicable).

Mmm, I just consider them as simple userland examples. They don't need
to manage PPS devices.

I can remove them from Documentation/pps/, no problems, but in my
modest opinion they are just documentation. :)

>  > +    static struct pps_source_info_s pps_ktimer_info = {
>  > +            name         : "ktimer",
>  > +            path         : "",
>  > +            mode         : PPS_CAPTUREASSERT | PPS_OFFSETASSERT | \
>  > +			   PPS_ECHOASSERT | \
>  > +                           PPS_CANWAIT | PPS_TSFMT_TSPEC,
>  > +            echo         : pps_ktimer_echo,
>  > +            owner        : THIS_MODULE,
>  > +    };
> 
>   should be
>     .name = "ktimer"
>   etc..

Fixed.

>  > +#include <linux/version.h>
> 
> This should be getting included automatically for you.

Fixed.

> On the whole, asides from these (very) minor nits, quite a clean
> submission compared to a lot of new driver submissions to lkml.
> Might want to run it through scripts/checkpatch.pl too to see
> if that picks up any more minor fluff.

Ok!

Ciao,

Rodolfo

-- 

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

  reply	other threads:[~2007-10-23 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 18:04 [PATCH] LinuxPPS - PPS support for Linux Rodolfo Giometti
2007-10-23 20:17 ` Dave Jones
2007-10-23 20:35   ` Rodolfo Giometti [this message]
2007-10-23 20:55   ` Rodolfo Giometti
2007-10-23 21:08     ` Roland Dreier
2007-10-24  7:00       ` Rodolfo Giometti
2007-10-25  8:39       ` Rodolfo Giometti
2007-10-25 20:32         ` 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=20071023203547.GO9748@enneenne.com \
    --to=giometti@enneenne.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.