* [Ksummit-discuss] printk unconference
@ 2014-08-12 14:33 Jan Kara
2014-08-12 14:38 ` Jiri Kosina
0 siblings, 1 reply; 2+ messages in thread
From: Jan Kara @ 2014-08-12 14:33 UTC (permalink / raw)
To: ksummit-discuss
Hello,
I've just requested slot for printk unconference on Tuesday Aug 19 at
11:00 (after morning break). I would like to find there some solution for
printk softlockups we are seeing which is acceptable for all parties (you
can read more details in my original proposal at
http://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000598.html).
Sasha and Jiri also expressed interest in discussing some topics regarding
printk in the thread (printk tinification, printk inside NMI - although
that is getting resolved AFAIK).
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Ksummit-discuss] printk unconference
2014-08-12 14:33 [Ksummit-discuss] printk unconference Jan Kara
@ 2014-08-12 14:38 ` Jiri Kosina
0 siblings, 0 replies; 2+ messages in thread
From: Jiri Kosina @ 2014-08-12 14:38 UTC (permalink / raw)
To: Jan Kara; +Cc: ksummit-discuss
On Tue, 12 Aug 2014, Jan Kara wrote:
> Sasha and Jiri also expressed interest in discussing some topics regarding
> printk in the thread (printk tinification, printk inside NMI - although
> that is getting resolved AFAIK).
Well, there are mutiple aproaches floating around for printk inside NMI,
and no final conclusion has been reached yet; so discussing this might be
worthwhile (even though Steven wouldn't be present, which is a bit
inconvenient, as his aproach seems to be the one that will hopefully head
towards merging).
--
Jiri Kosina
SUSE Labs
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-08-12 14:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-12 14:33 [Ksummit-discuss] printk unconference Jan Kara
2014-08-12 14:38 ` Jiri Kosina
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox