From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [Bulk] [PATCH] timer: vt8500: Move timer code to drivers/clocksource
Date: Mon, 14 Jan 2013 18:53:07 +1300 [thread overview]
Message-ID: <1358142787.28351.1.camel@gitbox> (raw)
In-Reply-To: <1358142455.25591.1.camel@gitbox>
> Oh grr.. forget this completely. It doesn't take into account the
> patches I already sent for WM8850.
>
> I guess it needs to be based on timer/cleanup + vt8500/wm8x50.
>
> Need a little advise on how to handle this one please :)
>
> Regards
> Tony P
Turns out the original patch applies cleanly on timer/cleanup +
vt8500/wm8x50 anyway so maybe it doesn't need to be rebased.
Let me know if I need to do anything (other than the -m to cleanup the
stats).
Regards
Tony P
WARNING: multiple messages have this Message-ID (diff)
From: Tony Prisk <linux@prisktech.co.nz>
To: Olof Johansson <olof@lixom.net>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm@kernel.org,
VT8500 Mailing List
<vt8500-wm8505-linux-kernel@googlegroups.com>
Subject: Re: [Bulk] [PATCH] timer: vt8500: Move timer code to drivers/clocksource
Date: Mon, 14 Jan 2013 18:53:07 +1300 [thread overview]
Message-ID: <1358142787.28351.1.camel@gitbox> (raw)
In-Reply-To: <1358142455.25591.1.camel@gitbox>
> Oh grr.. forget this completely. It doesn't take into account the
> patches I already sent for WM8850.
>
> I guess it needs to be based on timer/cleanup + vt8500/wm8x50.
>
> Need a little advise on how to handle this one please :)
>
> Regards
> Tony P
Turns out the original patch applies cleanly on timer/cleanup +
vt8500/wm8x50 anyway so maybe it doesn't need to be rebased.
Let me know if I need to do anything (other than the -m to cleanup the
stats).
Regards
Tony P
next prev parent reply other threads:[~2013-01-14 5:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 5:09 [GIT PULL] timer: vt8500: Move timer code to drivers/clocksource Tony Prisk
2013-01-14 5:09 ` Tony Prisk
2013-01-14 5:09 ` [PATCH] " Tony Prisk
2013-01-14 5:09 ` Tony Prisk
2013-01-14 5:13 ` [Bulk] " Tony Prisk
2013-01-14 5:13 ` Tony Prisk
2013-01-14 5:47 ` Tony Prisk
2013-01-14 5:47 ` Tony Prisk
2013-01-14 5:53 ` Tony Prisk [this message]
2013-01-14 5:53 ` Tony Prisk
2013-01-14 20:07 ` Olof Johansson
2013-01-14 20:07 ` Olof Johansson
2013-01-15 4:12 ` Tony Prisk
2013-01-15 4:12 ` Tony Prisk
2013-01-15 6:03 ` Olof Johansson
2013-01-15 6:03 ` Olof Johansson
2013-01-14 16:34 ` Stephen Warren
2013-01-14 16:34 ` Stephen Warren
2013-01-15 4:53 ` Tony Prisk
2013-01-15 4:53 ` Tony Prisk
2013-01-15 5:59 ` Olof Johansson
2013-01-15 5:59 ` Olof Johansson
2013-01-14 22:16 ` [GIT PULL] " Olof Johansson
2013-01-14 22:16 ` Olof Johansson
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=1358142787.28351.1.camel@gitbox \
--to=linux@prisktech.co.nz \
--cc=linux-arm-kernel@lists.infradead.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.