From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Johan Hovold <johan@kernel.org>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH RESEND] scsi: sun_esp: fix device reference leaks
Date: Tue, 27 Jun 2017 21:47:27 -0400 [thread overview]
Message-ID: <yq1tw30yjbk.fsf@oracle.com> (raw)
In-Reply-To: <20170621093509.GL6366@localhost> (Johan Hovold's message of "Wed, 21 Jun 2017 11:35:09 +0200")
Johan,
> Make sure to drop the reference to the dma device taken by
> of_find_device_by_node() on probe errors and on driver unbind.
Looks good to me.
Applied to 4.13/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-06-28 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 9:35 [PATCH RESEND] scsi: sun_esp: fix device reference leaks Johan Hovold
2017-06-28 1:47 ` Martin K. Petersen [this message]
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=yq1tw30yjbk.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=davem@davemloft.net \
--cc=jejb@linux.vnet.ibm.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox