From: "Jörn Engel" <joern@logfs.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, Takashi Iwai <tiwai@suse.de>,
Jens Axboe <axboe@kernel.dk>
Subject: [PULL] blockconsole and netconsole changes
Date: Wed, 1 May 2013 15:58:15 -0400 [thread overview]
Message-ID: <20130501195815.GA22691@logfs.org> (raw)
Linus,
please pull the bcon2 tree. It mainly contains blockconsole, which
allows directing printk to a block device (usually a cheap usb key).
Given your preference for WARN_ON_ONCE over BUG_ON, you might actually
have some personal interest.
CON_ALLDATA changes behaviour for blockconsole and netconsole. They
now receive all messages, independent of console_loglevel. I
personally have found this immensely useful and on a fundamental level
there really is no argument for having the same filter on a
user-interactive console and a debugging-only message dump.
All but the last two commit have soaked in -next for some weeks. The
last two are a trivial bugfix with several machineyears of testing and
a documentation change. Neither should collide with anyone else's
tree.
The following changes since commit 19f949f52599ba7c3f67a5897ac6be14bfcb1200:
Linux 3.8 (2013-02-18 15:58:34 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joern/bcon2.git master
for you to fetch changes up to e284f3493206d4268267db4557c7ee6f89ed2314:
netconsole: s/syslogd/cancd/ in documentation (2013-04-19 12:19:14 -0700)
----------------------------------------------------------------
Joern Engel (10):
do_mounts: constify name_to_dev_t parameter
add blockconsole version 1.1
printk: add CON_ALLDATA console flag
netconsole: use CON_ALLDATA
blockconsole: use CON_ALLDATA
bcon: add a release work struct
bcon: check for hdparm in bcon_tail
bcon: remove version 1.0 support
bcon: Fix wrap-around behaviour
netconsole: s/syslogd/cancd/ in documentation
Takashi Iwai (4):
blockconsole: Allow to pass a device file path to bcon_tail
blockconsole: Fix undefined MAX_RT_PRIO
blockconsole: Rename device_lock with bc_device_lock
blockconsole: Mark a local work struct static
Documentation/block/blockconsole.txt | 94 ++++
Documentation/block/blockconsole/bcon_tail | 82 +++
Documentation/block/blockconsole/mkblockconsole | 29 ++
Documentation/networking/netconsole.txt | 16 +-
block/partitions/Makefile | 1 +
block/partitions/blockconsole.c | 22 +
block/partitions/check.c | 3 +
block/partitions/check.h | 3 +
drivers/block/Kconfig | 6 +
drivers/block/Makefile | 1 +
drivers/block/blockconsole.c | 618 +++++++++++++++++++++++
drivers/net/netconsole.c | 2 +-
include/linux/blockconsole.h | 7 +
include/linux/console.h | 1 +
include/linux/mount.h | 2 +-
init/do_mounts.c | 2 +-
kernel/printk.c | 5 +-
17 files changed, 885 insertions(+), 9 deletions(-)
create mode 100644 Documentation/block/blockconsole.txt
create mode 100755 Documentation/block/blockconsole/bcon_tail
create mode 100755 Documentation/block/blockconsole/mkblockconsole
create mode 100644 block/partitions/blockconsole.c
create mode 100644 drivers/block/blockconsole.c
create mode 100644 include/linux/blockconsole.h
reply other threads:[~2013-05-01 21:25 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=20130501195815.GA22691@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--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