From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [GIT PULL] -Wstringop-overflow fixes for 5.19-rc1
Date: Tue, 24 May 2022 17:25:05 -0500 [thread overview]
Message-ID: <20220524222505.GA7242@embeddedor> (raw)
The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:
Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/Wstringop-overflow-fixes-5.19-rc1
for you to fetch changes up to 336feb502a715909a8136eb6a62a83d7268a353b:
drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency() (2022-05-04 14:59:26 -0500)
----------------------------------------------------------------
Wstringop-overflow fixes for 5.19-rc1
Hi Linus,
Please, pull the following patches that fix some -Wstringop-overflow
warnings when building with GCC-11. All the patches have been in
linux-next during the last development cycle.
This is part of the ongoing efforts to globally enable
-Wstringop-overflow.
Thanks
--
Gustavo
----------------------------------------------------------------
Gustavo A. R. Silva (3):
scsi: fcoe: Fix Wstringop-overflow warnings in fcoe_wwn_from_mac()
drm/amd/display: Fix Wstringop-overflow warnings in dc_link_dp.c
drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency()
drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c | 4 ++--
drivers/gpu/drm/amd/display/dc/inc/dc_link_dp.h | 4 ++--
drivers/gpu/drm/i915/intel_pm.c | 2 +-
drivers/scsi/fcoe/fcoe_ctlr.c | 2 +-
include/scsi/libfcoe.h | 3 ++-
5 files changed, 8 insertions(+), 7 deletions(-)
next reply other threads:[~2022-05-24 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:25 Gustavo A. R. Silva [this message]
2022-05-26 0:09 ` [GIT PULL] -Wstringop-overflow fixes for 5.19-rc1 pr-tracker-bot
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=20220524222505.GA7242@embeddedor \
--to=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.