From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Doug Anderson <dianders@chromium.org>,
Peter Hurley <peter@hurleysoftware.com>,
california.l.sullivan@intel.com, "Liakhovetski,
Guennadi" <guennadi.liakhovetski@intel.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
jslaby@suse.com, "Brian Norris" <briannorris@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
陈渐飞 <jeffy.chen@rock-chips.com>, 高美才 <eric.gao@rock-chips.com>,
phillip.raffeck@fau.de, anton.wuerfel@fau.de,
yegorslists@googlemail.com, matwey@sai.msu.ru,
tthayer@opensource.altera.com, linux-serial@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt
Date: Mon, 19 Dec 2016 19:35:20 +0200 [thread overview]
Message-ID: <1482168920.9552.101.camel@linux.intel.com> (raw)
In-Reply-To: <1482168788.9552.100.camel@linux.intel.com>
On Mon, 2016-12-19 at 19:33 +0200, Andy Shevchenko wrote:
> On Mon, 2016-12-19 at 09:12 -0800, Doug Anderson wrote:
> What I think is that the root cause of this is still unknown and
> either
> above looks like a hack.
One more link:
http://www.spinics.net/lists/linux-serial/msg22316.html
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-12-19 17:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 1:14 [PATCH] serial: 8250: Avoid "too much work" from bogus rx timeout interrupt Douglas Anderson
2016-12-19 12:59 ` Andy Shevchenko
2016-12-19 17:12 ` Doug Anderson
2016-12-19 17:33 ` Andy Shevchenko
2016-12-19 17:35 ` Andy Shevchenko [this message]
2016-12-19 17:54 ` Doug Anderson
2016-12-19 20:18 ` Andy Shevchenko
2016-12-19 21:13 ` Doug Anderson
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=1482168920.9552.101.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=anton.wuerfel@fau.de \
--cc=briannorris@chromium.org \
--cc=california.l.sullivan@intel.com \
--cc=dianders@chromium.org \
--cc=eric.gao@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=guennadi.liakhovetski@intel.com \
--cc=jeffy.chen@rock-chips.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--cc=peter@hurleysoftware.com \
--cc=phillip.raffeck@fau.de \
--cc=tthayer@opensource.altera.com \
--cc=yegorslists@googlemail.com \
/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.