All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay@vrfy.org>
Subject: [GIT PATCH] driver core (printk really) fixes for 3.5-rc6
Date: Wed, 11 Jul 2012 06:58:24 -0700	[thread overview]
Message-ID: <20120711135824.GA19620@kroah.com> (raw)

The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:

  Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-3.5-rc6

for you to fetch changes up to 5becfb1df5ac8e491338e64b1029685ccad4b39c:

  kmsg: merge continuation records while printing (2012-07-09 12:15:42 -0700)

----------------------------------------------------------------
printk fixes for 3.5-rc6

Here are some more printk fixes for 3.5-rc6.  They resolve all known
outstanding issues with the printk changes that have been happening.  They have
been tested by the people reporting the problems.

This hopefully should be it for the printk stuff for 3.5-final.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Kay Sievers (6):
      kmsg: escape the backslash character while exporting data
      kmsg: add the facility number to the syslog prefix
      kmsg: properly handle concurrent non-blocking read() from /proc/kmsg
      kmsg: make sure all messages reach a newly registered boot console
      kmsg: /proc/kmsg - support reading of partial log records
      kmsg: merge continuation records while printing

liu chuansheng (1):
      printk: replacing the raw_spin_lock/unlock with raw_spin_lock/unlock_irq

 kernel/printk.c | 202 +++++++++++++++++++++++++++++++++++---------------------
 1 file changed, 126 insertions(+), 76 deletions(-)

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120711135824.GA19620@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.