All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Kees Cook <keescook@chromium.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	David Howells <dhowells@redhat.com>
Cc: Sven Schnelle <svens@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] s390: disable -Warray-bounds
Date: Thu, 09 Jun 2022 11:56:47 +0200	[thread overview]
Message-ID: <168dbedc634a2994e9ab8f7e33930304da6140a7.camel@pengutronix.de> (raw)
In-Reply-To: <AEEBCF5D-8402-441D-940B-105AA718C71F@chromium.org>

Hi Kees,

On Mi, 2022-06-08 at 17:39 -0700, Kees Cook wrote:
[...]
> > See the attached patch for
> > 
> > (a) make the s390 "use -Wno-array-bounds for gcc-12" be generic
> > 
> > (b) fix the ipuv3-crtc.c one. IMX people?
> > 
> > (c) disable -Wdangling-pointer entirely for now
> 
> I'll take a look; thanks! Should I send them back as a pull request?

Does this refer to the whole patch, including (a) and (b), or am I to
pick up the ipuv3-crtc.c fix?

regards
Philipp

  parent reply	other threads:[~2022-06-09  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 13:43 [PATCH] s390: disable -Warray-bounds Sven Schnelle
2022-04-22 17:54 ` Kees Cook
2022-04-25  9:13   ` Heiko Carstens
2022-06-08 20:07   ` Linus Torvalds
2022-06-08 21:33     ` Kees Cook
2022-06-08 23:59       ` Linus Torvalds
2022-06-09  0:39         ` Kees Cook
2022-06-09  1:22           ` Linus Torvalds
2022-06-09  9:56           ` Philipp Zabel [this message]
2022-06-09 13:02             ` Kees Cook
2022-06-09 14:14           ` David Howells
2022-06-09 18:20             ` Linus Torvalds
2022-06-09 23:59               ` Dave Chinner
2022-06-10  1:18                 ` Linus Torvalds
2022-06-09  9:56         ` Philipp Zabel
2022-06-09 14:55         ` Nathan Chancellor
2022-06-09 18:51           ` Linus Torvalds

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=168dbedc634a2994e9ab8f7e33930304da6140a7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=agordeev@linux.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=festevam@gmail.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=svens@linux.ibm.com \
    --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.