* John Stultz wrote:
> Thanks Ingo for the very close review, and apologies for my poor
> keyboardmanship (I hope I didn't burn much of your good will here).
No problem. I usually fix typos up when the patch is otherwise good,
except for Git pulls, where I cannot, so I'm pushing back ...
>
On Sat, Mar 7, 2015 at 1:40 AM, Ingo Molnar wrote:
...
>
> Typo.
...
>
> Typo.
>
...
>
> Typo.
>
...
>
> Typo...
>
...
>
> Spurious space. I know they are cheap, but still.
And a big D with a circle around it. Back to grade-school with me. :)
Thanks Ingo for the very close review, and apologies
On Sat, Mar 7, 2015 at 1:40 AM, Ingo Molnar mi...@kernel.org wrote:
...
Typo.
...
Typo.
...
Typo.
...
Typo...
...
Spurious space. I know they are cheap, but still.
And a big D with a circle around it. Back to grade-school with me. :)
Thanks Ingo for the very close review, and
* John Stultz john.stu...@linaro.org wrote:
Thanks Ingo for the very close review, and apologies for my poor
keyboardmanship (I hope I didn't burn much of your good will here).
No problem. I usually fix typos up when the patch is otherwise good,
except for Git pulls, where I cannot, so I'm
* John Stultz wrote:
> It was suggested that the underflow/overflow protection
> should probably throw some sort of warning out, rather
> then just silently fixing the issue.
Typo.
> So this patch adds some warnings here. The flag variables
> used are not protected by locks, but since we
* John Stultz john.stu...@linaro.org wrote:
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
Typo.
So this patch adds some warnings here. The flag variables
used are not protected by locks,
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
So this patch adds some warnings here. The flag variables
used are not protected by locks, but since we can't print
from the reading functions, just
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
So this patch adds some warnings here. The flag variables
used are not protected by locks, but since we can't print
from the reading functions, just
On Thu, Jan 22, 2015 at 04:09:23PM -0800, John Stultz wrote:
> #ifdef CONFIG_DEBUG_TIMEKEEPING
> +#define WARNINGFREQ (HZ*300) /* 5 minute rate-limiting */
> +/*
> + * These simple flag variables are managed
> + * without locks, which is racy, but ok since
> + * we don't really care about being
On Thu, Jan 22, 2015 at 04:09:23PM -0800, John Stultz wrote:
#ifdef CONFIG_DEBUG_TIMEKEEPING
+#define WARNINGFREQ (HZ*300) /* 5 minute rate-limiting */
+/*
+ * These simple flag variables are managed
+ * without locks, which is racy, but ok since
+ * we don't really care about being super
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
So this patch adds some warnings here. The flag variables
used are not protected by locks, but since we can't print
from the reading functions, just
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
So this patch adds some warnings here. The flag variables
used are not protected by locks, but since we can't print
from the reading functions, just
12 matches
Mail list logo
