All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Baptiste Reynal <b.reynal@virtualopensystems.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	kvm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] vfio: platform: Fix reset module leak in error path
Date: Wed, 11 Apr 2018 10:09:31 +0200	[thread overview]
Message-ID: <20180411080930.6knha76gu5f6qgnw@verge.net.au> (raw)
In-Reply-To: <1523375627-23746-2-git-send-email-geert+renesas@glider.be>

On Tue, Apr 10, 2018 at 05:53:46PM +0200, Geert Uytterhoeven wrote:
> If the IOMMU group setup fails, the reset module is not released.
> 
> Fixes: b5add544d677d363 ("vfio, platform: make reset driver a requirement by default")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>

Reviewed-by: Simon Horman <horms+renesas@verge.net.au>

  reply	other threads:[~2018-04-11  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 15:53 [PATCH v2 0/2] vfio: platform: Improve reset support Geert Uytterhoeven
2018-04-10 15:53 ` [PATCH v2 1/2] vfio: platform: Fix reset module leak in error path Geert Uytterhoeven
2018-04-11  8:09   ` Simon Horman [this message]
2018-04-10 15:53 ` [PATCH v2 2/2] vfio: platform: Add generic DT reset controller support Geert Uytterhoeven
2018-04-11  8:22   ` Philipp Zabel
2018-04-11  8:43     ` Geert Uytterhoeven
2018-04-11  8:22   ` Simon Horman
2018-04-11  8:39     ` Geert Uytterhoeven
2018-04-12  6:54       ` Simon Horman

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=20180411080930.6knha76gu5f6qgnw@verge.net.au \
    --to=horms@verge.net.au \
    --cc=alex.williamson@redhat.com \
    --cc=b.reynal@virtualopensystems.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@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.