From: "Jörn Engel" <joern@logfs.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiri Kosina <jkosina@suse.cz>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
cxie@redhat.com, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH] printk: Print cpu number along with time
Date: Wed, 4 Jun 2014 19:15:06 -0400 [thread overview]
Message-ID: <20140604231506.GA31276@logfs.org> (raw)
In-Reply-To: <20140428172219.4be61cf7.akpm@linux-foundation.org>
On Mon, 28 April 2014 17:22:19 -0700, Andrew Morton wrote:
> On Mon, 28 Apr 2014 19:40:39 -0400 J__rn Engel <joern@logfs.org> wrote:
> > On Thu, 24 April 2014 15:40:24 -0400, J__rn Engel wrote:
> > > On Wed, 23 April 2014 20:52:47 -0400, J__rn Engel wrote:
> > > >
> > > > I use the patch below for some time now. While it doesn't avoid the
> > > > log pollution in the first place, it lessens the impact somewhat.
> > >
> > > Added a config option and ported it to current -linus. Andrew, would
> > > you take this patch?
> >
> > Andrew? Did you dislike this patch for some reason or just miss it in
> > the thread?
>
> Neither ;) I try to respond in some way to all patches unless I think it's clear
> to the originator why I took no action. And I think I'm pretty good at
> not losing stuff.
>
> otoh, it has only been four days, three of which I spent offline...
Ping. It is closer to 40 days now. Can I fault this patch back into
your memory?
Jörn
--
Good warriors cause others to come to them and do not go to others.
-- Sun Tzu
next prev parent reply other threads:[~2014-06-04 23:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 16:53 [PATCH RFC] sysrq: rcu-ify __handle_sysrq Rik van Riel
2014-04-23 20:04 ` Andrew Morton
2014-04-23 20:44 ` Rik van Riel
2014-04-23 21:39 ` Jiri Kosina
2014-04-23 21:41 ` Andrew Morton
2014-04-23 21:44 ` Jiri Kosina
2014-04-23 21:49 ` Andrew Morton
2014-04-23 21:37 ` Jiri Kosina
2014-04-23 21:42 ` Rik van Riel
2014-04-23 21:51 ` Jiri Kosina
2014-04-24 1:46 ` Paul E. McKenney
2014-04-24 13:04 ` [PATCH RFC] sysrq,rcu: suppress RCU stall warnings while sysrq runs Rik van Riel
2014-04-24 15:16 ` Paul E. McKenney
2014-04-25 5:35 ` Mike Galbraith
2014-04-24 0:52 ` [PATCH RFC] sysrq: rcu-ify __handle_sysrq Jörn Engel
2014-04-24 19:40 ` [PATCH] printk: Print cpu number along with time Jörn Engel
2014-04-24 19:58 ` Greg Kroah-Hartman
2014-04-24 21:23 ` Jörn Engel
2014-04-24 22:12 ` Jiri Kosina
2014-04-24 22:18 ` David Rientjes
2014-04-24 22:21 ` Jiri Kosina
2014-04-24 23:29 ` Jörn Engel
2014-04-24 22:20 ` Greg Kroah-Hartman
2014-04-28 23:40 ` Jörn Engel
2014-04-29 0:22 ` Andrew Morton
2014-06-04 23:15 ` Jörn Engel [this message]
2014-06-04 23:28 ` Andrew Morton
2014-06-04 23:49 ` Jörn Engel
2014-09-09 17:16 ` Jörn Engel
2014-09-10 21:26 ` Andrew Morton
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=20140604231506.GA31276@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=cxie@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.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