dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	gregkh@linux-foundation.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] Component helper updates
Date: Tue, 24 Nov 2015 00:38:59 +0100	[thread overview]
Message-ID: <20151123233859.GC22339@lunn.ch> (raw)
In-Reply-To: <20151123160210.GR8644@n2100.arm.linux.org.uk>

On Mon, Nov 23, 2015 at 04:02:11PM +0000, Russell King - ARM Linux wrote:
> Greg,
> 
> These four patches update the component helper by:

Hi Russell

Is there any documentation for the component helper, in particular,
when devm_ can be used?

It seems like slaves should only do a component_add() in their probe
function, and then do resource allocation using devm_* in the bind
callback?

It seems like a master device can however use devm_ in its probe
function?

Thanks
	Andrew

  parent reply	other threads:[~2015-11-23 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 16:02 [PATCH 0/4] Component helper updates Russell King - ARM Linux
2015-11-23 16:02 ` [PATCH 1/4] component: remove old add_components method Russell King
2015-11-23 23:26   ` Andrew Lunn
2015-12-07 17:06   ` Andrew Lunn
2015-11-23 16:02 ` [PATCH 2/4] component: move check for unbound master into try_to_bring_up_masters() Russell King
2015-11-23 16:02 ` [PATCH 3/4] component: track components via array rather than list Russell King
2015-11-23 16:02 ` [PATCH 4/4] component: add support for releasing match data Russell King
2015-11-23 23:38 ` Andrew Lunn [this message]
2015-12-07 15:01 ` [PATCH 0/4] Component helper updates Russell King - ARM Linux
2016-01-04 17:25   ` Russell King - ARM Linux

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=20151123233859.GC22339@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    /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