public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Waiman Long <longman@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Yang Shi <yang.shi@linux.alibaba.com>,
	Arnd Bergmann <arnd@arndb.de>, Dmitry Safonov <dima@arista.com>
Subject: Re: [PATCH] debugobjects: Move printk out of db lock critical sections
Date: Thu, 13 Dec 2018 10:21:59 +0100	[thread overview]
Message-ID: <20181213092159.GE5289@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20181213025940.GF4860@jagdpanzerIV>

On Thu, Dec 13, 2018 at 11:59:40AM +0900, Sergey Senozhatsky wrote:
> On (12/12/18 17:28), Waiman Long wrote:
> > 
> > warning from lockdep as reported in https://lkml.org/lkml/2018/12/11/143.
> > 
> 
> That link shows an empty page, lkml.org is quite unstable. Let's
> use this one instead:
> 
> https://lore.kernel.org/lkml/20181211091154.GL23332@shao2-debian/T/#u

Better yet:

  https://lkml.kernel.org/r/20181211091154.GL23332@shao2-debian

  reply	other threads:[~2018-12-13  9:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 22:28 [PATCH] debugobjects: Move printk out of db lock critical sections Waiman Long
2018-12-12 23:39 ` Andrew Morton
2018-12-13 22:01   ` Waiman Long
2018-12-13  2:03 ` Sergey Senozhatsky
2018-12-13 19:59   ` Waiman Long
2018-12-13  2:59 ` Sergey Senozhatsky
2018-12-13  9:21   ` Peter Zijlstra [this message]
2018-12-13  4:35 ` Dmitry Safonov
2018-12-13  5:18   ` Sergey Senozhatsky
2018-12-13  5:54     ` Dmitry Safonov
2018-12-13  9:00       ` Sergey Senozhatsky
2018-12-13 22:10   ` Waiman Long
2018-12-14 18:06     ` Dmitry Safonov
2018-12-14 18:21       ` Waiman Long

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=20181213092159.GE5289@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dima@arista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=yang.shi@linux.alibaba.com \
    /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