public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org,
	Peter Hurley <peter@hurleysoftware.com>
Subject: [PATCH v2 0/3] n_tty_read() helper cleanups
Date: Fri, 27 Nov 2015 14:11:01 -0500	[thread overview]
Message-ID: <1448651464-4103-1-git-send-email-peter@hurleysoftware.com> (raw)
In-Reply-To: <1446993310-7681-1-git-send-email-peter@hurleysoftware.com>

Hi Greg,

This series rebases a couple of already-sent patches on top of the
EOF push bug fix, "n_tty: Fix poll() after buffer-limited eof push read",
and adds a third to reduce branching (which hopefully clarifies the
copy algorithm some).

I will also resend the "Rework tty audit" series, which requires this
series.

Regards,

Peter Hurley (3):
  n_tty: Uninline tty_copy_to_user()
  n_tty: Clarify copy_from_read_buf()
  n_tty: Reduce branching in canon_copy_from_read_buf()

 drivers/tty/n_tty.c | 48 +++++++++++++++++++++++++-----------------------
 1 file changed, 25 insertions(+), 23 deletions(-)

-- 
2.6.3


  parent reply	other threads:[~2015-11-27 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 14:35 [PATCH] n_tty: Clarify copy_from_read_buf() Peter Hurley
2015-11-08 14:35 ` [PATCH] n_tty: Uninline tty_copy_to_user() Peter Hurley
2015-11-27 19:11 ` Peter Hurley [this message]
2015-11-27 19:11   ` [PATCH v2 1/3] " Peter Hurley
2015-11-27 19:11   ` [PATCH v2 2/3] n_tty: Clarify copy_from_read_buf() Peter Hurley
2015-11-27 19:11   ` [PATCH v2 3/3] n_tty: Reduce branching in canon_copy_from_read_buf() Peter Hurley

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=1448651464-4103-1-git-send-email-peter@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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