All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: James Bottomley <james.bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	James Smart <james.smart@emulex.com>
Subject: Re: [PATCH 1/2] scsi_transport_fc: Introduce scsi_host_{get,put}()
Date: Mon, 30 Nov 2015 12:34:52 -0500	[thread overview]
Message-ID: <yq1vb8jgzlv.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <564F9190.5090103@sandisk.com> (Bart Van Assche's message of "Fri, 20 Nov 2015 13:33:04 -0800")

>>>>> "Bart" == Bart Van Assche <bart.vanassche@sandisk.com> writes:

Bart,

Bart> Use scsi_host_{get,put}() instead of open-coding these functions.
Bart> Compile-tested only.

Do you want me to queue this as a general cleanup for 4.5 (independently
of the leak patch)?

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2015-11-30 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 21:30 [PATCH 0/2] Fix a scsi_host_dev_release() memory leak Bart Van Assche
2015-11-20 21:33 ` [PATCH 1/2] scsi_transport_fc: Introduce scsi_host_{get,put}() Bart Van Assche
2015-11-22 15:03   ` Christoph Hellwig
2015-11-24 12:43   ` Johannes Thumshirn
2015-11-30 17:34   ` Martin K. Petersen [this message]
2015-11-30 17:37     ` Bart Van Assche
2015-11-30 22:47       ` Martin K. Petersen
2015-11-20 21:34 ` [PATCH 2/2] Fix a memory leak in scsi_host_dev_release() Bart Van Assche
2015-11-26  3:40 ` [PATCH 0/2] Fix a scsi_host_dev_release() memory leak Martin K. Petersen
2015-11-26  7:35   ` 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=yq1vb8jgzlv.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=james.smart@emulex.com \
    --cc=linux-scsi@vger.kernel.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.