From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v02] powerpc/mobility: Fix node detach/rename problem
Date: Wed, 8 Aug 2018 10:37:56 -0500 [thread overview]
Message-ID: <19f9e274-26ae-2ae5-de9f-c0fcd6c00570@linux.vnet.ibm.com> (raw)
In-Reply-To: <87zhxx9cs7.fsf@concordia.ellerman.id.au>
On 08/08/2018 09:02 AM, Michael Ellerman wrote:
> Michael Bringmann <mwb@linux.vnet.ibm.com> writes:
>> diff --git a/arch/powerpc/platforms/pseries/mobility.c b/arch/powerpc/platforms/pseries/mobility.c
>> index e245a88..efc9442 100644
>> --- a/arch/powerpc/platforms/pseries/mobility.c
>> +++ b/arch/powerpc/platforms/pseries/mobility.c
>> @@ -22,6 +22,9 @@
>> #include <asm/rtas.h>
>> #include "pseries.h"
>>
>> +extern int of_free_phandle_cache(void);
>> +extern void of_populate_phandle_cache(void);
>
> We don't do that, they should be in a header.
>
> But that's a minor problem given that the patch doesn't compile, because
> both those functions are static.
I am building against the latest 'linux-ppc' kernel. It includes patch
Commit b9952b5218added5577e4a3443969bc20884cea9 Mon Sep 17 00:00:00 2001
From: Frank Rowand <frank.rowand@sony.com>
Date: Thu, 12 Jul 2018 14:00:07 -0700
Subject: of: overlay: update phandle cache on overlay apply and remove
which makes the functions static. I will rebuild and test with an
earlier version if you will specify which one.
>
> Presumably you have a hack in your tree to make them non-static?
> Please try and compile your patches in a clean tree before sending.
>
> cheers
Regards,
Michael
--
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line 363-5196
External: (512) 286-5196
Cell: (512) 466-0650
mwb@linux.vnet.ibm.com
next prev parent reply other threads:[~2018-08-08 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 14:21 [PATCH v02] powerpc/mobility: Fix node detach/rename problem Michael Bringmann
2018-08-08 14:02 ` Michael Ellerman
2018-08-08 15:37 ` Michael Bringmann [this message]
2018-08-08 15:39 ` Michael Bringmann
2018-08-10 1:46 ` Michael Ellerman
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=19f9e274-26ae-2ae5-de9f-c0fcd6c00570@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).