From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] of: export of_get_next_parent
Date: Sun, 21 Apr 2013 20:56:38 +0200 [thread overview]
Message-ID: <51743666.2070006@gmail.com> (raw)
In-Reply-To: <CACVXFVMuUn=0LLWxJO62gp6uugNej-kwC0k_LMGWozGRxcx6Vg@mail.gmail.com>
Hi,
On 04/21/2013 02:11 PM, Ming Lei wrote:
> On Wed, Apr 10, 2013 at 5:47 PM, Ming Lei<ming.lei@canonical.com> wrote:
>> The function is called by at least three drivers now:
>>
>> pinctrl
>> mfd/vexpress
>> v4l2-core
>>
>> The 3rd one can be built as module, so export the function to
>> avoid build failure.
>>
>> Cc: Grant Likely<grant.likely@secretlab.ca>
>> Cc: Rob Herring<rob.herring@calxeda.com>
>> Cc: devicetree-discuss@lists.ozlabs.org
>> Signed-off-by: Ming Lei<ming.lei@canonical.com>
>> ---
>> drivers/of/base.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>> index c6443de..a2a0ddc 100644
>> --- a/drivers/of/base.c
>> +++ b/drivers/of/base.c
>> @@ -382,6 +382,7 @@ struct device_node *of_get_next_parent(struct device_node *node)
>> raw_spin_unlock_irqrestore(&devtree_lock, flags);
>> return parent;
>> }
>> +EXPORT_SYMBOL(of_get_next_parent);
>
> Gentle ping.
>
> Without the patch, the below build failure is produced every time on -next tree:
A similar patch has been queued in the media tree [1]. It should soon
appear in -next.
[1]
http://git.linuxtv.org/mchehab/media-next.git/commitdiff/6695be6863b75620ffa6d422965680ce785cb7c8
Sorry for the trouble.
Thanks,
Sylwester
prev parent reply other threads:[~2013-04-21 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 9:47 [PATCH] of: export of_get_next_parent Ming Lei
2013-04-21 12:11 ` Ming Lei
2013-04-21 18:56 ` Sylwester Nawrocki [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=51743666.2070006@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).