From: Luotao Fu <l.fu@pengutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg KH <gregkh@suse.de>, Luotao Fu <l.fu@pengutronix.de>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ilya Dryomov <idryomov@gmail.com>
Subject: Re: Problem with tty changes in linux-next
Date: Tue, 6 Jul 2010 17:48:12 +0200 [thread overview]
Message-ID: <20100706154812.GA2813@pengutronix.de> (raw)
In-Reply-To: <201007061735.02881.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
Hi,
On Tue, Jul 06, 2010 at 05:35:02PM +0200, Arnd Bergmann wrote:
> On Tuesday 06 July 2010 17:14:54 Greg KH wrote:
> > I should get to this today and push it into the next
> > linux-next release.
>
> Ok, thanks!
>
> On Tuesday 06 July 2010 16:40:52 Ilya Dryomov wrote:
> > I had the same issue. Here is the patch:
> >
> > https://patchwork.kernel.org/patch/108700/
>
> Yes, that's the one. It would be good to get another confirmation
> from Luotao Fu that this fixes all the problems with missing characters.
> As I mentioned, the boot-time warning will get taken care of by
> a different patch, but can be safely ignored.
I picked up the patch and did a quick test. The console message printing
works so far.
Thanks
Cheers
Luotao Fu
--
Pengutronix e.K. | Dipl.-Ing. Luotao Fu |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-07-06 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 13:04 Problem with tty changes in linux-next Luotao Fu
2010-07-06 14:23 ` Arnd Bergmann
2010-07-06 14:40 ` Ilya Dryomov
2010-07-06 15:14 ` Greg KH
2010-07-06 15:35 ` Arnd Bergmann
2010-07-06 15:48 ` Luotao Fu [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=20100706154812.GA2813@pengutronix.de \
--to=l.fu@pengutronix.de \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.