From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Jiri Slaby <jslaby@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] assorted TTY code cleanups
Date: Tue, 18 Apr 2017 18:02:53 +0200 [thread overview]
Message-ID: <20170418160253.GA25958@kroah.com> (raw)
In-Reply-To: <20170412223717.20890-1-nicolas.pitre@linaro.org>
On Wed, Apr 12, 2017 at 06:37:13PM -0400, Nicolas Pitre wrote:
> Those are, I hope, fairly uncontrovertial patches that should require very
> little review as they mostly do code movement providing nice cleanups.
> No logical changes are introduced by those patches.
>
> My minitty patch series is based on top of this, and given the timing,
> I don't expect it to go upstream just yet. However the following patches
> could be merged separately for the next merge window.
All look good and are now applied, thanks.
greg k-h
prev parent reply other threads:[~2017-04-18 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 22:37 [PATCH 0/4] assorted TTY code cleanups Nicolas Pitre
2017-04-12 22:37 ` [PATCH 1/4] console: move console_init() out of tty_io.c Nicolas Pitre
2017-05-03 18:13 ` Andy Shevchenko
2017-05-03 19:06 ` Greg Kroah-Hartman
2017-05-03 19:16 ` Andy Shevchenko
2017-05-03 19:47 ` Greg Kroah-Hartman
2017-04-12 22:37 ` [PATCH 2/4] tty: move baudrate handling code to a file of its own Nicolas Pitre
2017-04-12 22:37 ` [PATCH 3/4] tty: split job control support into " Nicolas Pitre
2017-04-12 22:37 ` [PATCH 4/4] serial: small Makefile reordering Nicolas Pitre
2017-04-18 16:02 ` Greg Kroah-Hartman [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=20170418160253.GA25958@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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 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.