The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Hulk Robot <hulkci@huawei.com>,
	Jason Yan <yanaijie@huawei.com>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] gcc-plugins fixes for v5.12-rc2
Date: Fri, 5 Mar 2021 15:14:44 -0800	[thread overview]
Message-ID: <202103051512.624654ABB8@keescook> (raw)


Hi Linus,

Please pull these tiny gcc-plugin fixes for v5.12-rc2. These issues
are small but have been reported a couple times now by static analyzers,
so best to get them fixed to reduce the noise. :)

Thanks!

-Kees

The following changes since commit fe07bfda2fb9cdef8a4d4008a409bb02f35f1bd8:

  Linux 5.12-rc1 (2021-02-28 16:05:19 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugins-v5.12-rc2

for you to fetch changes up to 5477edcacaacb8af8169450180a1d3bd0dfb9c99:

  gcc-plugins: latent_entropy: remove unneeded semicolon (2021-03-01 19:19:50 -0800)

----------------------------------------------------------------
gcc-plugins fixes for v5.12-rc2

- Fix coding style issues (Jason Yan)

----------------------------------------------------------------
Jason Yan (2):
      gcc-plugins: structleak: remove unneeded variable 'ret'
      gcc-plugins: latent_entropy: remove unneeded semicolon

 scripts/gcc-plugins/latent_entropy_plugin.c | 2 +-
 scripts/gcc-plugins/structleak_plugin.c     | 3 +--
 2 files changed, 2 insertions(+), 3 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2021-03-05 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 23:14 Kees Cook [this message]
2021-03-06  1:35 ` [GIT PULL] gcc-plugins fixes for v5.12-rc2 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=202103051512.624654ABB8@keescook \
    --to=keescook@chromium.org \
    --cc=hulkci@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yanaijie@huawei.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