[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170503194728.GB28882@kroah.com>
Date: Wed, 3 May 2017 12:47:28 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Nicolas Pitre <nicolas.pitre@...aro.org>,
Petr Mladek <pmladek@...e.com>, Jiri Slaby <jslaby@...e.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] console: move console_init() out of tty_io.c
On Wed, May 03, 2017 at 10:16:00PM +0300, Andy Shevchenko wrote:
> On Wed, May 3, 2017 at 10:06 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > 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@...aro.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,
>
> Ah, good.
>
> > why do you think it is
> > not applied?
>
> I have a tree based on top of most recent linux-next with
> (potentially) conflicting patches. Besides that I just grepped the
> code and found no changes in today's linux-next.
Ah crap! I never pushed that tree out to the world, it was stuck on my
laptop... Ugh, doing that now...
greg k-h
Powered by blists - more mailing lists