linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>, mpe@ellerman.id.au
Cc: npiggin@gmail.com, naveen@kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4/6] powerpc: fix sparse warnings
Date: Sun, 18 May 2025 09:24:43 +0530	[thread overview]
Message-ID: <350af9cb-c8ef-49af-b9f3-4992a09b4e4d@linux.ibm.com> (raw)
In-Reply-To: <897452a6-4c78-4aa6-9f6a-18e8720076ae@csgroup.eu>



On 5/2/25 3:46 PM, Christophe Leroy wrote:
> 
> 
> Le 22/04/2025 à 15:10, Madhavan Srinivasan a écrit :
>> structs are local to the source and does not need to
>> be in global scope, so make it static.
>>
>> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
>> ---
>>   arch/powerpc/kernel/btext.c              | 2 +-
>>   arch/powerpc/kernel/setup-common.c       | 2 +-
>>   arch/powerpc/platforms/powernv/opal.c    | 2 +-
>>   arch/powerpc/platforms/pseries/lparcfg.c | 2 +-
>>   4 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/kernel/btext.c b/arch/powerpc/kernel/btext.c
>> index 7f63f1cdc6c3..fc7f5a5b6d76 100644
>> --- a/arch/powerpc/kernel/btext.c
>> +++ b/arch/powerpc/kernel/btext.c
>> @@ -40,7 +40,7 @@ static int dispDeviceRect[4] __force_data;
>>   static unsigned char *dispDeviceBase __force_data;
>>   static unsigned char *logicalDisplayBase __force_data;
>>   -unsigned long disp_BAT[2] __initdata = {0, 0};
>> +static unsigned long disp_BAT[2] __initdata = {0, 0};
> 
> disp_BAT is used in assembly, has to remain global:
> 
> arch/powerpc/kernel/head_book3s_32.S:   addis   r8,r3,disp_BAT@ha
> arch/powerpc/kernel/head_book3s_32.S:   addi    r8,r8,disp_BAT@l

Thought I did a top folder level sweep for this. My bad. 
Nice catch. Will drop this. 

Thanks

> 
> Christophe
> 



  reply	other threads:[~2025-05-18  3:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 13:10 [PATCH 0/6] Fixes for shellcheck/sparse warnings Madhavan Srinivasan
2025-04-22 13:10 ` [PATCH 1/6] powerpc/kvm: Fix sparse warning Madhavan Srinivasan
2025-04-22 13:10 ` [PATCH 2/6] powerpc/xmon: fix sparse warning "Using plain integer as NULL pointer" Madhavan Srinivasan
2025-05-02 10:08   ` Christophe Leroy
2025-05-18  3:51     ` Madhavan Srinivasan
2025-04-22 13:10 ` [PATCH 3/6] powerpc/perf:make isa207_pmu_format_group struct static Madhavan Srinivasan
2025-05-07 11:52   ` kernel test robot
2025-04-22 13:10 ` [PATCH 4/6] powerpc: fix sparse warnings Madhavan Srinivasan
2025-05-02 10:16   ` Christophe Leroy
2025-05-18  3:54     ` Madhavan Srinivasan [this message]
2025-05-07 11:11   ` kernel test robot
2025-04-22 13:10 ` [PATCH 5/6] powerpc/prom_init: Fix shellcheck warnings Madhavan Srinivasan
2025-04-22 13:42   ` Stephen Rothwell
2025-04-22 13:10 ` [PATCH 6/6] powerpc/boot/install.sh: " Madhavan Srinivasan
2025-04-22 13:46   ` Stephen Rothwell
2025-04-23  8:44 ` [PATCH 0/6] Fixes for shellcheck/sparse warnings Venkat Rao Bagalkote

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=350af9cb-c8ef-49af-b9f3-4992a09b4e4d@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@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;
as well as URLs for NNTP newsgroup(s).