Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754047AbbK3RKh (ORCPT <rfc822;w@1wt.eu>);
	Mon, 30 Nov 2015 12:10:37 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:51210 "EHLO
	mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752140AbbK3RKf (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 30 Nov 2015 12:10:35 -0500
Date: Mon, 30 Nov 2015 09:10:34 -0800
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-serial@vger.kernel.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Peter Hurley <peter@hurleysoftware.com>,
        Rob Herring <robherring2@gmail.com>
Subject: Re: The console log is doubled if earlycon is enabled
Message-ID: <20151130171034.GA14366@kroah.com>
References: <CAK7LNAT5L2uxJ6i-QEYqw9qFLyvADu_E0F5VVTOPqyHbLodTCg@mail.gmail.com>
 <20151128000451.GB22297@kroah.com>
 <CAK7LNARFa8Q1t6RwwQVhTrtXJxnJBQw8QHnbpfNfHouEiGdK0w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAK7LNARFa8Q1t6RwwQVhTrtXJxnJBQw8QHnbpfNfHouEiGdK0w@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1143
Lines: 36

On Mon, Nov 30, 2015 at 02:53:49PM +0900, Masahiro Yamada wrote:
> 2015-11-28 9:04 GMT+09:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> > On Fri, Nov 27, 2015 at 07:21:06PM +0900, Masahiro Yamada wrote:
> >> Hi,
> >>
> >>
> >> If I add "earlycon" to the kernel parameter, the log message
> >> on the earlycon is also displayed to the regular console.
> >> In other words, the same log messages are displayed twice.
> >>
> >> I noticed this problem on v4.4-rc1.
> >> It has not been fixed in the mainline yet, I think.
> >>
> >> Anybody who has a clue?
> >> (I have not done git-bisect yet.)
> >
> > Can you do 'git bisect'?
> 
> 
> The same problem happened on v4.3.
> (I think I just did not notice the problem before.)
> 
> So, the bad commit is not in the last merge window.

Is it ok for 4.2?  4.1?  Finding out where this started to "fail" would
be good to know...

thanks,

greg k-h

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/