From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Udo van den Heuvel <udovdh@xs4all.nl>,
linux-kernel@vger.kernel.org,
Alexander Gordeev <lasaine@lvk.cs.msu.su>,
Rodolfo Giometti <giometti@linux.it>
Subject: Re: hardpps patch by Alexander Gordeev
Date: Thu, 14 Oct 2010 15:05:41 -0700 [thread overview]
Message-ID: <20101014150541.bbbbd74d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101014145751.5fc4adb6.rdunlap@xenotime.net>
On Thu, 14 Oct 2010 14:57:51 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Mon, 11 Oct 2010 19:25:35 +0200 Udo van den Heuvel wrote:
>
> > Hello,
> >
> > Can anybody here explain the status of Alexander Gordeev's harddpps patches?
> > Are they on the list to be included in the kernel?
> > Is work on the patches needed?
> >
> > Thanks for your comment.
>
> It's in Andrew Morton's mmotm tree.
> Where/when it goes from there to Linus's tree is a good question.
I didn't merge it into 2.6.36 and it's looking doubtful for 2.6.37.
There were a number of issues identified during review and afaik they
remain up in the air.
My notes-to-self from the series file:
pps-trivial-fixes.patch
pps-declare-variables-where-they-are-used-in-switch.patch
#pps-fix-race-in-pps_fetch-handler.patch: Vitezslav Samel <vitezslav@samel.cz> q, TBU
pps-fix-race-in-pps_fetch-handler.patch
pps-unify-timestamp-gathering.patch
#pps-access-pps-device-by-direct-pointer.patch: Rodolfo issues
pps-access-pps-device-by-direct-pointer.patch
pps-convert-printk-pr_-to-dev_.patch
pps-move-idr-stuff-to-ppsc.patch
pps-add-async-pps-event-handler.patch
pps-add-async-pps-event-handler-fix.patch
pps-dont-disable-interrupts-when-using-spin-locks.patch
pps-use-bug_on-for-kernel-api-safety-checks.patch
pps-simplify-conditions-a-bit.patch
ntp-add-hardpps-implementation.patch
#pps-capture-monotonic_raw-timestamps-as-well.patch: John had Q, TBU
pps-capture-monotonic_raw-timestamps-as-well.patch
pps-add-kernel-consumer-support.patch
pps-add-parallel-port-pps-client.patch
pps-add-parallel-port-pps-signal-generator.patch
(where TBU = "to be updated").
There may be other issues - one would need to go back and review the review
thread.
prev parent reply other threads:[~2010-10-14 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 17:25 hardpps patch by Alexander Gordeev Udo van den Heuvel
2010-10-14 21:57 ` Randy Dunlap
2010-10-14 22:05 ` Andrew Morton [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=20101014150541.bbbbd74d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=giometti@linux.it \
--cc=lasaine@lvk.cs.msu.su \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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