mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: bgoswami@codeaurora.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, srinivas.kandagatla@linaro.org
Subject: Re: [PATCH][RESEND 2] component: enhance handling of devres group for master
Date: Thu, 26 Jul 2018 09:26:21 +0100	[thread overview]
Message-ID: <20180726082621.GW17271@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1532585188-7831-1-git-send-email-bgoswami@codeaurora.org>

On Wed, Jul 25, 2018 at 11:06:28PM -0700, bgoswami@codeaurora.org wrote:
> From: Banajit Goswami <bgoswami@codeaurora.org>
> 
> The devres group opened for a master is left open-ended (without
> devres_group_close) even after bind() is complete. Similarly, while
> releasing the devres resources for master, the most recently opened
> devres group is selected, and released without identifying the
> targeted group. As the devres group opened before master bind was
> never closed, there may have unintended consequences of releasing
> devres resources that were allocated after master bind() function
> was complete.

... as intended, because this layers on top of the driver model.
You are aware that the driver model leaves its implicit group open
as well?

I think you need to explain why you need this - what is the problem
scenario that you are encountering.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 13.8Mbps down 630kbps up
According to speedtest.net: 13Mbps down 490kbps up

      reply	other threads:[~2018-07-26  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  6:06 bgoswami
2018-07-26  8:26 ` Russell King - ARM Linux [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=20180726082621.GW17271@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=bgoswami@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.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

all inboxes | Powered by JetHome®