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
Subject: [PATCH 0/4] firewire, some more logging related patches
Date: Sat, 18 Feb 2012 21:58:24 +0100	[thread overview]
Message-ID: <20120218215824.5b2359bf@stein> (raw)

Forthcoming:
  * firewire: sbp2: identify to driver core as "firewire_sbp2", not "sbp2"
  * firewire: net: identify to driver core as "firewire_net", not "net"
  * firewire: net: prefix all log messages with interface name
  * firewire: core: prefix log messages with card name

 drivers/firewire/core-card.c        |   28 ++++++++++---
 drivers/firewire/core-cdev.c        |   10 ++--
 drivers/firewire/core-device.c      |   60 +++++++++++++---------------
 drivers/firewire/core-topology.c    |   18 ++++----
 drivers/firewire/core-transaction.c |    4 -
 drivers/firewire/core.h             |    6 ++
 drivers/firewire/net.c              |   45 ++++++++++++---------
 drivers/firewire/sbp2.c             |    6 --
 include/linux/firewire.h            |    3 -
 9 files changed, 100 insertions(+), 80 deletions(-)
-- 
Stefan Richter
-=====-===-- --=- =--=-
http://arcgraph.de/sr/

             reply	other threads:[~2012-02-18 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18 20:58 Stefan Richter [this message]
2012-02-18 21:01 ` [PATCH 1/4] firewire: sbp2: identify to driver core as "firewire_sbp2", not "sbp2" Stefan Richter
2012-02-18 21:01 ` [PATCH 2/4] firewire: net: identify to driver core as "firewire_net", not "net" Stefan Richter
2012-02-18 21:02 ` [PATCH 3/4] firewire: net: prefix all log messages with interface name Stefan Richter
2012-02-18 21:32   ` Joe Perches
2012-02-19 11:48     ` Stefan Richter
2012-02-18 21:03 ` [PATCH 4/4] firewire: core: prefix log messages with card name 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=20120218215824.5b2359bf@stein \
    --to=stefanr@s5r6.in-berlin.de \
    --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