public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Kyle McMartin <kyle@kernel.org>,
	Dave Jones <davej@codemonkey.org.uk>, Jan Kara <jack@suse.com>,
	Calvin Owens <calvinowens@fb.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	kernel test robot <ying.huang@linux.intel.com>,
	kernel-team@fb.com,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] printk: clear console_may_schedule on panic flushing
Date: Mon, 11 Jan 2016 17:09:27 -0500	[thread overview]
Message-ID: <20160111220927.GL1898@mtj.duckdns.org> (raw)
In-Reply-To: <20160111135951.b5f81c02c6d2054164f618af@linux-foundation.org>

Hello,

On Mon, Jan 11, 2016 at 01:59:51PM -0800, Andrew Morton wrote:
> Got that, thanks.  Because the patch has significant information
> content I'd normally make it a standalone thing, but as it's destined
> for -stable I think I'll scrunch it into
> printk-do-cond_resched-between-lines-while-outputting-to-consoles.patch
> and merge the changelogs.

Sure thing.

> You didn't comment on Sergey's observations
> (https://lkml.org/lkml/2015/12/2/1192), but I'm believing this is
> a separate issue and that this patch is still good.

Missed that one somehow.  Will respond.

Thanks.

-- 
tejun

  reply	other threads:[~2016-01-11 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11  3:08 [lkp] [printk] db43e77a44: BUG: sleeping function called from invalid context at kernel/printk/printk.c:2328 kernel test robot
2016-01-11 18:43 ` [PATCH] printk: clear console_may_schedule on panic flushing Tejun Heo
2016-01-11 21:59   ` Andrew Morton
2016-01-11 22:09     ` Tejun Heo [this message]
2016-01-11 22:25       ` Tejun Heo
2016-01-12 13:50     ` Sergey Senozhatsky

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=20160111220927.GL1898@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=calvinowens@fb.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jack@suse.com \
    --cc=kernel-team@fb.com \
    --cc=kyle@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=ying.huang@linux.intel.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