Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: zhaoxiao <zhaoxiao@uniontech.com>,
	tsbogend@alpha.franken.de, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/mips/boot/compressed/string.c: Fix build warnings
Date: Wed, 19 May 2021 15:14:47 +0100	[thread overview]
Message-ID: <N8YCTQ.J6CD851ZEGJ73@crapouillou.net> (raw)
In-Reply-To: <8d01b52e-6687-a624-6a76-97b4b71d999e@flygoat.com>

Hi,

Le mer., mai 19 2021 at 22:00:07 +0800, Jiaxun Yang 
<jiaxun.yang@flygoat.com> a écrit :
> 
> 
> 在 2021/5/19 16:44, zhaoxiao 写道:
>> Fixes the following W=1 kernel build warning(s):
>> arch/mips/boot/compressed/string.c:11:7: warning: no previous 
>> prototype for 'memcpy' [-Wmissing-prototypes]
>>   void *memcpy(void *dest, const void *src, size_t n)
>>         ^~~~~~
>> arch/mips/boot/compressed/string.c:22:7: warning: no previous 
>> prototype for 'memset' [-Wmissing-prototypes]
>>   void *memset(void *s, int c, size_t n)
>>         ^~~~~~
>> arch/mips/boot/compressed/string.c:32:15: warning: no previous 
>> prototype for 'memmove' [-Wmissing-prototypes]
>>   void * __weak memmove(void *dest, const void *src, size_t n)
> Hi Xiao,
> 
> Are you sure you know what you're doing?
> 
> They're supposed to be called by external reference in vmlinuz.
> Marking them static makes no sense.

I was wondering that too.

I suppose including <asm/string.h> should be enough to fix the warnings.

Cheers,
-Paul

>>                 ^~~~~~~
>> 
>> Signed-off-by: zhaoxiao <zhaoxiao@uniontech.com>
>> ---
>>   arch/mips/boot/compressed/string.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>> 
>> diff --git a/arch/mips/boot/compressed/string.c 
>> b/arch/mips/boot/compressed/string.c
>> index 0b593b709228..d28996509f91 100644
>> --- a/arch/mips/boot/compressed/string.c
>> +++ b/arch/mips/boot/compressed/string.c
>> @@ -8,7 +8,7 @@
>>   #include <linux/compiler_attributes.h>
>>   #include <linux/types.h>
>>   \x7f-void *memcpy(void *dest, const void *src, size_t n)
>> +static void *memcpy(void *dest, const void *src, size_t n)
>>   {
>>   	int i;
>>   	const char *s = src;
>> @@ -19,7 +19,7 @@ void *memcpy(void *dest, const void *src, size_t n)
>>   	return dest;
>>   }
>>   \x7f-void *memset(void *s, int c, size_t n)
>> +static void *memset(void *s, int c, size_t n)
>>   {
>>   	int i;
>>   	char *ss = s;
>> @@ -29,7 +29,7 @@ void *memset(void *s, int c, size_t n)
>>   	return s;
>>   }
>>   \x7f-void * __weak memmove(void *dest, const void *src, size_t n)
>> +static void * __weak memmove(void *dest, const void *src, size_t n)
>>   {
>>   	unsigned int i;
>>   	const char *s = src;
> 



      reply	other threads:[~2021-05-19 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19  8:44 [PATCH] arch/mips/boot/compressed/string.c: Fix build warnings zhaoxiao
2021-05-19 14:00 ` Jiaxun Yang
2021-05-19 14:14   ` Paul Cercueil [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=N8YCTQ.J6CD851ZEGJ73@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=zhaoxiao@uniontech.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