From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <jbottomley@parallels.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/6] First batch of logging cleanups
Date: Wed, 04 Jun 2014 07:50:52 +0200 [thread overview]
Message-ID: <538EB3BC.7060401@suse.de> (raw)
In-Reply-To: <yq11tv54p7w.fsf@sermon.lab.mkp.net>
On 06/04/2014 12:12 AM, Martin K. Petersen wrote:
>>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
>
> Hannes> Hi all, this is the first patch of my SCSI logging cleanup. The
> Hannes> basic idea here is to use dev_printk() and friends throughout
> Hannes> the midlayer, so that any logging messages are attached with the
> Hannes> correct device information.
>
> All patches look good to me (except I'd really like to see SCSI logging
> die a horrible death. Sadly it's an exposed user interface and therefore
> hard to nuke).
>
Hehe.
That's next in line.
Plan is to move all SCSI_LOGGING_ML_XXX over to scsi_tracing.
And then slowly working my way up.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-04 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 11:22 [PATCH 0/6] First batch of logging cleanups Hannes Reinecke
2014-06-03 11:22 ` [PATCH 1/6] scsi: Implement sr_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 2/6] scsi: Implement sg_printk() Hannes Reinecke
2014-06-03 13:32 ` Douglas Gilbert
2014-06-03 11:22 ` [PATCH 3/6] scsi: Implement ch_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 4/6] scsi: Implement st_printk() Hannes Reinecke
2014-06-03 11:22 ` [PATCH 5/6] scsi: use dev_printk() variants for ioctl Hannes Reinecke
2014-06-03 11:22 ` [PATCH 6/6] scsi: use dev_printk variants where possible Hannes Reinecke
2014-10-22 22:29 ` Elliott, Robert (Server Storage)
2014-06-03 22:12 ` [PATCH 0/6] First batch of logging cleanups Martin K. Petersen
2014-06-04 5:50 ` Hannes Reinecke [this message]
2014-06-11 12:08 ` Christoph Hellwig
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=538EB3BC.7060401@suse.de \
--to=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).