* Timer breakage in net-next
@ 2017-10-27 8:05 David Howells
2017-10-27 9:09 ` Kees Cook
0 siblings, 1 reply; 2+ messages in thread
From: David Howells @ 2017-10-27 8:05 UTC (permalink / raw)
To: davem, keescook; +Cc: dhowells, netdev, linux-kernel
Hi Dave, Kees,
Is it possible to get this timer fix:
https://patchwork.ozlabs.org/patch/828333/
timer: Provide wrappers safe for use with LOCKDEP
included in net-next?
You can add my Tested-by line.
David
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Timer breakage in net-next
2017-10-27 8:05 Timer breakage in net-next David Howells
@ 2017-10-27 9:09 ` Kees Cook
0 siblings, 0 replies; 2+ messages in thread
From: Kees Cook @ 2017-10-27 9:09 UTC (permalink / raw)
To: David Howells; +Cc: David S. Miller, Network Development, LKML
On Fri, Oct 27, 2017 at 10:05 AM, David Howells <dhowells@redhat.com> wrote:
> Hi Dave, Kees,
>
> Is it possible to get this timer fix:
>
> https://patchwork.ozlabs.org/patch/828333/
>
> timer: Provide wrappers safe for use with LOCKDEP
>
> included in net-next?
FWIW, the LOCKDEP warnings are false positives. The fix includes
updates to one new API function, which would be an additional patch.
When I talked with Thomas, it sounded like it was better just to wait
for the merge window instead of trying to figure out a way to land
this separately in other trees. Obviously this is up to Dave, but it
seemed like a merge of tip/timers/core into net-next would be
confusing.
> You can add my Tested-by line.
Thanks for checking it!
-Kees
--
Kees Cook
Pixel Security
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-27 9:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-27 8:05 Timer breakage in net-next David Howells
2017-10-27 9:09 ` Kees Cook
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®