[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20101014150541.bbbbd74d.akpm@linux-foundation.org>
Date: Thu, 14 Oct 2010 15:05:41 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Udo van den Heuvel <udovdh@...all.nl>,
linux-kernel@...r.kernel.org,
Alexander Gordeev <lasaine@....cs.msu.su>,
Rodolfo Giometti <giometti@...ux.it>
Subject: Re: hardpps patch by Alexander Gordeev
On Thu, 14 Oct 2010 14:57:51 -0700
Randy Dunlap <rdunlap@...otime.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@...el.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists