From: Jan Kara <jack@suse.cz>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] printk unconference
Date: Tue, 12 Aug 2014 16:33:33 +0200 [thread overview]
Message-ID: <20140812143333.GB3270@quack.suse.cz> (raw)
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
next reply other threads:[~2014-08-12 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:33 Jan Kara [this message]
2014-08-12 14:38 ` Jiri Kosina
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=20140812143333.GB3270@quack.suse.cz \
--to=jack@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox