public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Carl Karsten <carl@personnelware.com>
Subject: [PATCH 0/3] firewire: some simple kernel log changes
Date: Tue, 20 Dec 2011 21:30:17 +0100	[thread overview]
Message-ID: <20111220213017.75ff380c@stein> (raw)

I wanted to hold off with posting the following few patches because I still
want to add some firewire-core and firewire-net logging related updates as
well.  But since Carl may be interested in patch 2/3 right now, here they are.

1/3 firewire: do not expose globally unique IDs in the kernel log
2/3 firewire: ohci: use dev_printk API
3/3 firewire: sbp2: use dev_printk API

 drivers/firewire/core-device.c |    8 -
 drivers/firewire/net.c         |    8 -
 drivers/firewire/ohci.c        |  185 +++++++++++++++++++++++------------------
 drivers/firewire/sbp2.c        |   93 +++++++++++---------
 4 files changed, 165 insertions(+), 129 deletions(-)
-- 
Stefan Richter
-=====-==-== ==-- =-=--
http://arcgraph.de/sr/

             reply	other threads:[~2011-12-20 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 20:30 Stefan Richter [this message]
2011-12-20 20:31 ` [PATCH 1/3] firewire: do not expose globally unique IDs in the kernel log Stefan Richter
2011-12-20 20:58   ` Carl Karsten
2011-12-20 23:10     ` Stefan Richter
2011-12-20 23:42       ` Carl Karsten
2011-12-20 23:43       ` Stefan Richter
2011-12-20 23:50         ` Carl Karsten
2011-12-20 20:32 ` [PATCH 2/3] firewire: ohci: use dev_printk API Stefan Richter
2011-12-20 20:34 ` [PATCH 3/3] firewire: sbp2: " Stefan Richter

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=20111220213017.75ff380c@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=carl@personnelware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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