From: Thomas Gleixner <tglx@linutronix.de>
To: Ashton Holmes <scoopta@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Michal Necasek <michal.necasek@oracle.com>,
stern@rowland.harvard.edu, michael.thayer@oracle.com,
knut.osmundsen@oracle.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
rt@linutronix.de
Subject: Re: [patch 0/2] timers: Fix base clock forwarding issues
Date: Thu, 27 Oct 2016 22:42:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610272241400.4913@nanos> (raw)
In-Reply-To: <CA+OSeukz5OSzHdezcUpL1hYj9FurYxu8Nwm5CToLjvyCNvesbQ@mail.gmail.com>
On Thu, 27 Oct 2016, Ashton Holmes wrote:
> On Sat, Oct 22, 2016 at 4:10 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > Several people have reported USB timeout issues starting in 4.8 which are
> > related to the timer wheel overhaul.
> >
> > The following two patches adress the brown paperbag bugs in that code.
> >
> > Thanks,
> >
> > tglx
> >
> Sorry it took me so long to reply. I've been rather busy. I've been running
> kernel 4.8.4 with these two patches for the past 2 days and have yet to
> encounter any issues. Thanks.
Thanks for confirmation and all the help with tracking this down!
tglx
>
prev parent reply other threads:[~2016-10-27 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 11:07 Thomas Gleixner
2016-10-22 11:07 ` [patch 1/2] timers: Prevent base clock rewind when forwarding clock Thomas Gleixner
2016-10-25 14:58 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner
2016-10-22 11:07 ` [patch 2/2] timers: Prevent base clock corruption when forwarding Thomas Gleixner
2016-10-25 14:59 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner
[not found] ` <CA+OSeukz5OSzHdezcUpL1hYj9FurYxu8Nwm5CToLjvyCNvesbQ@mail.gmail.com>
2016-10-27 20:42 ` Thomas Gleixner [this message]
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=alpine.DEB.2.20.1610272241400.4913@nanos \
--to=tglx@linutronix.de \
--cc=knut.osmundsen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.com \
--cc=michal.necasek@oracle.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rt@linutronix.de \
--cc=scoopta@gmail.com \
--cc=stern@rowland.harvard.edu \
/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 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®