From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Petr Mladek <pmladek@suse.com>, Jiri Slaby <jslaby@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] console: move console_init() out of tty_io.c
Date: Wed, 3 May 2017 12:06:28 -0700 [thread overview]
Message-ID: <20170503190628.GA25456@kroah.com> (raw)
In-Reply-To: <CAHp75Vciv7B+G_9s+9X=tRFGhqNSdeLu8LD7GcURcZ8Tab9JqQ@mail.gmail.com>
On Wed, May 03, 2017 at 09:13:51PM +0300, Andy Shevchenko wrote:
> +Cc: Petr
>
> On Thu, Apr 13, 2017 at 1:37 AM, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> > All the console driver handling code lives in printk.c.
> > Move console_init() there as well so console support can still be used
> > when the TTY code is configured out. No logical changes from this patch.
> >
>
> So, I missed cover letter.
> The question is what is this all for and why it's not applied yet?
It's in my tty tree to go to Linus for 4.12-rc1, why do you think it is
not applied?
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-03 19:06 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 [this message]
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 ` [PATCH 0/4] assorted TTY code cleanups Greg Kroah-Hartman
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=20170503190628.GA25456@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=pmladek@suse.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.