public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Greg Kroah-Hartmann <greg@kroah.com>
Cc: Joe Perches <joe@perches.com>, Kay Sievers <kay@vrfy.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 3.5-rc6 printk formatting problem during oom-kill.
Date: Tue, 10 Jul 2012 20:11:45 -0400	[thread overview]
Message-ID: <20120711001145.GB10518@redhat.com> (raw)
In-Reply-To: <20120709205631.GA22980@kroah.com>

On Mon, Jul 09, 2012 at 01:56:31PM -0700, Greg Kroah-Hartman wrote:
 > > > > That single patch doesn't apply cleanly to Linus'
 > > > > 8c84bf4166a4698296342841a549bbee03860ac0
 > > > > 
 > > > > What else is necessary?
 > > > > 
 > > > > Your tree seems to have a collection of random patches.
 > > > > 
 > > > > It might be useful to clone Linus' tree and produce a
 > > > > branch with all the necessary printk patches in it so
 > > > > someone else could pull it.
 > > > 
 > > > They should all now be in my driver-core-next branch that will show up
 > > > in the next linux-next release, so having a separate tree isn't
 > > > necessary.
 > > 
 > > I don't think so.
 > > 
 > > There are real defects in the existing code.
 > > 
 > > These are patches that are necessary _now_.
 > > not for a -next 3.6 future.
 > 
 > Oops, sorry, I ment to type, "driver-core-linus" above.

Can you get this to Linus asap please ? I just had an oops that scrolled
off the screen because the Code: line suffers the same problem.
Thankfully serial console caught most of it, but I had to hand-edit
a lot of crap just to make it readable again.

	Dave


  reply	other threads:[~2012-07-11  0:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 18:03 3.5-rc6 printk formatting problem during oom-kill Dave Jones
2012-07-09 18:27 ` Kay Sievers
2012-07-09 18:48   ` Kay Sievers
2012-07-09 20:31     ` Joe Perches
2012-07-09 20:40       ` Greg Kroah-Hartmann
2012-07-09 20:44         ` Joe Perches
2012-07-09 20:48           ` Kay Sievers
2012-07-09 21:08             ` Joe Perches
2012-07-09 20:56           ` Greg Kroah-Hartmann
2012-07-11  0:11             ` Dave Jones [this message]
2012-07-11  0:15               ` Greg Kroah-Hartmann
2012-07-12  0:54     ` Dave Jones
2012-07-12 13:52       ` Kay Sievers
2012-07-12 14:05         ` Dave Jones
2012-07-12 16:47           ` Kay Sievers
2012-07-12 17:02             ` Dave Jones
2012-07-12 17:11           ` Linus Torvalds
2012-07-12 18:25             ` Kay Sievers
2012-07-12 22:28               ` Kay Sievers

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=20120711001145.GB10518@redhat.com \
    --to=davej@redhat.com \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --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