From: Jason Gunthorpe <jgg@mellanox.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Matteo Croce <mcroce@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
linuxppc-dev@lists.ozlabs.org, op <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tty: hvc: latency break regression fixes
Date: Wed, 5 Sep 2018 12:50:56 -0600 [thread overview]
Message-ID: <20180905185056.GF421@mellanox.com> (raw)
In-Reply-To: <20180905121439.23809-1-npiggin@gmail.com>
On Wed, Sep 05, 2018 at 10:14:36PM +1000, Nicholas Piggin wrote:
> Hi Greg,
>
> Here are fixes for a few regressions that came in with my
> carelessness with the irq latency work for the hvc subsystem.
> These were independently reported in 2 configurations, and I
> confirmed with another.
>
> I think those went upstream via Michael's tree, but he's away
> at the moment so if you would be able to consider them for
> the tty tree that would be appreciated.
Series works for me too, thanks.
Tested-by: Jason Gunthorpe <jgg@mellanox.com>
Jason
prev parent reply other threads:[~2018-09-05 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 12:14 [PATCH 0/3] tty: hvc: latency break regression fixes Nicholas Piggin
2018-09-05 12:14 ` [PATCH 1/3] tty: hvc: hvc_poll() fix read loop hang Nicholas Piggin
2018-09-05 12:14 ` [PATCH 2/3] tty: hvc: hvc_poll() fix read loop batching Nicholas Piggin
2018-09-05 12:14 ` [PATCH 3/3] tty: hvc: hvc_write() fix break condition Nicholas Piggin
2018-09-06 13:10 ` Nicholas Piggin
2018-09-05 18:50 ` Jason Gunthorpe [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=20180905185056.GF421@mellanox.com \
--to=jgg@mellanox.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcroce@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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.