public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: udovdh@xs4all.nl, linux-kernel@vger.kernel.org,
	Rodolfo Giometti <giometti@linux.it>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: LinuxPPS status?
Date: Fri, 8 May 2009 15:59:35 -0700	[thread overview]
Message-ID: <20090508155935.3e88e49e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090508112722.040e99ee@lxorguk.ukuu.org.uk>

On Fri, 8 May 2009 11:27:22 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Fri, 08 May 2009 12:17:39 +0200
> Udo van den Heuvel <udovdh@xs4all.nl> wrote:
> 
> > Hello,
> > 
> > Can anybody please give a summary of the things needing work before 
> > LinuxPPS can go into the kernel?
> > Andrew posted something in february but are his objections still valid?
> > 
> > Can we just fix the final bits and have it in the kernel whenever the 
> > first occasion comes along?
> 
> If you are getting no feedback just submit it next merge window. Either
> its offended nobody or they've forgotten to notice - in both cases
> submitting it will have the desired effect.

As far as I know the master version is sitting in -mm.  This thing has
gone on for so long and with such large intervals between activity that
I've forgotten what the outstanding issues are, if any.

I have a note here that Christoph had requested that the pps header
file be split in some fashion (user and kernel?) but that doesn't
appear to have happened in my copy of the patch.

Probably it would be best to start again, resend the patch with 1000 cc's,
re-review and actually get it over the line.


  reply	other threads:[~2009-05-08 23:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 10:17 LinuxPPS status? Udo van den Heuvel
2009-05-08 10:27 ` Alan Cox
2009-05-08 22:59   ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-22  7:29 Udo van den Heuvel

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=20090508155935.3e88e49e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=giometti@linux.it \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --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