[U-Boot] [PATCH v1 (WIP) 00/16] [Timer]API Rewrite

[Graeme Russ <graeme.russ@gmail.com>]

On 28/06/11 21:40, Graeme Russ wrote:
> The following series is a work-in-progress revamp of the timer API. The aim
> is to create a new userland API consisting of the following functions
> (along with a few arch level support functions):
> 

[snip]

> Graeme Russ (16):
>   [Timer]Fix misuse of ARM *timer_masked() functions outside arch/arm
>   [Timer]Remove calls to set_timer outside arch/
>   [Timer]Remove calls to set_timer in arch/
>   [Timer]Allow reset_timer() only for Nios2
>   [Timer]Remove reset_timer() for non-Nios2 arches
>   [Timer]Fix at91rm9200/spi.c timer usage
>   [Timer]Remove reset_timer_masked()
>   [Timer]Create new userland timer API
>   [Timer]Replace get_timer() usage in drivers/block/
>   [Timer]Replace get_timer() usage in driver/mtd and driver/block
>   [Timer]Remove reset_timer() completely
>   [Timer]Replace get_timer() usage in drivers/
>   [Timer]Replace get_timer() usage in net/
>   [Timer]Replace get_timer() usage in common/
>   [Timer]Replace get_timer() usage in board/
>   [Timer]Replace get_timer() usage in arch/

OK, I'm back from holidays and there has only been a few minor comments so
far. I take that as either a) the work is generally OK as is and there are
no major objections or b) everyone is too busy to care ;) - I'll work with
option a) and rebase/re-spin this series. Now although the board/ patch was
too big for the list, it looks like it hit patchwork OK, so I will leave
that as is.

Wolfgang, a few quick question for you:

1) I understand that you would like each individual patch in the series to
have the in-reply-to header set to the individual parent patch and not have
the whole series in-reply-to the first (00/16) patch? (It will be a bit of
a PITA to set in-reply-to for 16 individual patches, but I will do if that
is the way you want it)

2) I will be changing the name of the series to a) drop the WIP and b)
change "[Timer]" to "Timer:" as per Mike Frysinger's comment - Does this
pose any issue to you provided the in-reply-to remains intact

3) The board/ series is a 'Big Patch' but it made it to Patchwork - Are you
happy for me to leave it as-is? As it's in patchwork, can I forget about
putting it on the Big Patches wiki?

4) I'm thinking about creating an Timer branch in my x86 repository and
pushing the whole series through there - From there I can keep it rebased
and simply issue a pull request when it's finished (and testers can just
pull it if they want). Does this sound like a good plan?

5) Most importantly - Have you had a chance to look at this series? Is it
to your liking?

Regards,

Graeme