[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+1xoqdgckzNAtHFwgjVHj169ZYn5rna1HNwudrQKegr4DAqVw@mail.gmail.com>
Date: Fri, 11 May 2012 17:09:42 +0200
From: Sasha Levin <levinsasha928@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Jiri Slaby <jslaby@...e.cz>, Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
Jiri Slaby <jirislaby@...il.com>
Subject: Re: [PATCH 3/3] tty_lock: Localise the lock
On Fri, May 11, 2012 at 4:52 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> The printk rework should now be working again in linux-next. Is it
> still causing problems for you?
Mostly does, there's still a minor issue regarding showing timestamps
on each line in the log, I've commented about it in the original
thread (
http://permalink.gmane.org/gmane.linux.kernel/1295580).
It's fairly visible in the lockdep spew, since lockdep does lots of
this "printk("\nsomething\n");"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists