The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>,
	Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Michal Hocko <mhocko@kernel.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: lockdep warning: console vs. mem hotplug
Date: Tue, 21 Mar 2017 14:04:50 +0900	[thread overview]
Message-ID: <20170321050450.GA25958@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170321044421.GB448@jagdpanzerIV.localdomain>

[..]
> 3) move add_timer() out of sclp_con_lock console in sclp_console_write().
	^^^^^^^^^^^^
	I take it back. Won't improve anything.

	-ss

  reply	other threads:[~2017-03-21  5:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 16:43 lockdep warning: console vs. mem hotplug Sebastian Ott
2017-03-21  4:44 ` Sergey Senozhatsky
2017-03-21  5:04   ` Sergey Senozhatsky [this message]
2017-03-25  0:04   ` Sergey Senozhatsky
2017-03-25  1:08     ` Steven Rostedt
2017-03-25  1:37       ` Sergey Senozhatsky
2017-03-25 10:59     ` Sebastian Ott
2017-03-28 14:22     ` Michal Hocko
2017-03-28 16:00       ` Petr Mladek
2017-03-29  7:31         ` Michal Hocko
2017-03-30  9:45           ` Petr Mladek
2017-03-30  3:59       ` Sergey Senozhatsky
2017-07-24 12:46   ` Sebastian Ott
2017-07-24 13:32     ` Sergey Senozhatsky
2017-03-24 16:39 ` Steven Rostedt
2017-03-24 16:57   ` Sebastian Ott
2017-03-25  0:00   ` Sergey Senozhatsky
2017-03-25  1:00     ` Steven Rostedt

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=20170321050450.GA25958@jagdpanzerIV.localdomain \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=sebott@linux.vnet.ibm.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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