dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Philipp Zabel <philipp.zabel@gmail.com>
Cc: devel@driverdev.osuosl.org, dri-devel@lists.freedesktop.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC v2 3/8] component: add support for component match array
Date: Thu, 26 Jun 2014 15:46:01 +0100	[thread overview]
Message-ID: <20140626144601.GS32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CA+gwMcdO5P-Yu+-FeHHGxkKwObsATL-ThVDwmEm2_cZ3enUXPQ@mail.gmail.com>

On Thu, Jun 26, 2014 at 02:34:17PM +0200, Philipp Zabel wrote:
> Hi Russell,
> 
> On Tue, Jun 24, 2014 at 9:29 PM, Russell King
> <rmk+kernel@arm.linux.org.uk> wrote:
> [...]
> > +/*
> > + * Add a component to be matched.
> > + *
> > + * The match array is first created or extended if necessary.
> > + */
> > +void component_match_add(struct device *dev, struct component_match **matchptr,
> > +       int (*compare)(struct device *, void *), void *compare_data)
> > +{
> > +       struct component_match *match = *matchptr;
> > +
> > +       if (IS_ERR(match))
> > +               return;
> > +
> > +       if (!match || match->num == match->alloc) {
> > +               size_t new_size = match ? match->alloc + 16 : 15;
> > +
> > +               match = component_match_realloc(dev, match, new_size);
> > +
> > +               *matchptr = match;
> > +
> > +               if (IS_ERR(match))
> > +                       return;
> > +       }
> > +
> > +       match->compare[match->num].fn = compare;
> > +       match->compare[match->num].data = compare_data;
> > +       match->num++;
> > +}
> 
> component_match_add should be exported.

Fixed, thanks.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-06-26 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 19:28 [PATCH RFC v2 0/8] component helper improvements Russell King - ARM Linux
2014-06-24 19:28 ` [PATCH RFC v2 1/8] component: fix missed cleanup in case of devres failure Russell King
2014-06-24 19:29 ` [PATCH RFC v2 2/8] component: ignore multiple additions of the same component Russell King
2014-06-24 19:29 ` [PATCH RFC v2 3/8] component: add support for component match array Russell King
2014-06-26 12:34   ` Philipp Zabel
2014-06-26 14:46     ` Russell King - ARM Linux [this message]
2014-07-01 14:22       ` Russell King - ARM Linux
2014-07-02 15:26         ` Inki Dae
2014-07-02 16:15           ` Russell King - ARM Linux
2014-08-30 21:33           ` Russell King - ARM Linux
2014-09-01  2:47             ` Inki Dae
2014-06-24 19:29 ` [PATCH RFC v2 4/8] drm: msm: update to use component match support Russell King
2014-06-24 19:29 ` [PATCH RFC v2 5/8] imx-drm: " Russell King
2014-06-24 19:29 ` [PATCH RFC v2 6/8] component: remove old add_components method Russell King
2014-06-24 19:29 ` [PATCH RFC v2 7/8] component: move check for unbound master into try_to_bring_up_masters() Russell King
2014-06-24 19:29 ` [PATCH RFC v2 8/8] component: track components via array rather than list Russell King

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=20140626144601.GS32514@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=philipp.zabel@gmail.com \
    /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