From: patchwork-bot+linux-soc@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: soc@kernel.org
Subject: Re: [PATCH] [RESEND] ARM: sharpsl_param: work around -Wstringop-overread warning
Date: Tue, 05 Oct 2021 13:50:09 +0000 [thread overview]
Message-ID: <163344180946.2242.16359198571616577949.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210927145332.2784005-1-arnd@kernel.org>
Hello:
This patch was applied to soc/soc.git (refs/heads/arm/fixes):
On Mon, 27 Sep 2021 16:53:25 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc warns that accessing a pointer based on a numeric constant may
> be an offset into a NULL pointer, and would therefore has zero
> accessible bytes:
>
> arch/arm/common/sharpsl_param.c: In function ‘sharpsl_save_param’:
> arch/arm/common/sharpsl_param.c:43:9: error: ‘memcpy’ reading 64 bytes from a region of size 0 [-Werror=stringop-overread]
> 43 | memcpy(&sharpsl_param, param_start(PARAM_BASE), sizeof(struct sharpsl_param_info));
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [RESEND] ARM: sharpsl_param: work around -Wstringop-overread warning
https://git.kernel.org/soc/soc/c/34186b48d29b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-05 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 14:53 [PATCH] [RESEND] ARM: sharpsl_param: work around -Wstringop-overread warning Arnd Bergmann
2021-09-27 14:53 ` Arnd Bergmann
2021-09-27 14:55 ` Daniel Mack
2021-09-27 14:55 ` Daniel Mack
2021-10-05 13:50 ` patchwork-bot+linux-soc [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=163344180946.2242.16359198571616577949.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=arnd@kernel.org \
--cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.