* John Stultz wrote:
> On Fri, Mar 13, 2015 at 1:58 AM, Ingo Molnar wrote:
> > * John Stultz wrote:
> >> On Thu, Mar 12, 2015 at 2:19 AM, Ingo Molnar wrote:
> >> > * John Stultz wrote:
> >> >> New in v4:
> >> >> * Lots and lots of typo corrections and minor cleanups suggested
> >> >> by In
On Fri, Mar 13, 2015 at 1:58 AM, Ingo Molnar wrote:
> * John Stultz wrote:
>> On Thu, Mar 12, 2015 at 2:19 AM, Ingo Molnar wrote:
>> > * John Stultz wrote:
>> >> New in v4:
>> >> * Lots and lots of typo corrections and minor cleanups suggested
>> >> by Ingo.
>> >> * Dropped "Remove clocksourc
* John Stultz wrote:
> On Thu, Mar 12, 2015 at 2:19 AM, Ingo Molnar wrote:
> > * John Stultz wrote:
> >> New in v4:
> >> * Lots and lots of typo corrections and minor cleanups suggested
> >> by Ingo.
> >> * Dropped "Remove clocksource_max_deferment()" patch
> >> * Added "Rename __clocksource
On Thu, Mar 12, 2015 at 2:19 AM, Ingo Molnar wrote:
> * John Stultz wrote:
>> New in v4:
>> * Lots and lots of typo corrections and minor cleanups suggested
>> by Ingo.
>> * Dropped "Remove clocksource_max_deferment()" patch
>> * Added "Rename __clocksource_updatefreq_*..." patch
>> * I realize
* John Stultz wrote:
> So here is another round of this series, which is the result of
> earlier discussions with Linus and his suggestions around
> improvements to clocksource validation in the hope we can more
> easily catch bad hardware.
>
> There's also a few cleanups Linus suggested as wel
So here is another round of this series, which is the result of
earlier discussions with Linus and his suggestions around
improvements to clocksource validation in the hope we can more
easily catch bad hardware.
There's also a few cleanups Linus suggested as well as a few I've been
meaning to get
6 matches
Mail list logo
