All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jack Vogel <jack.vogel@oracle.com>,
	"mustafa.ismail@intel.com" <mustafa.ismail@intel.com>,
	"shiraz.saleem@intel.com" <shiraz.saleem@intel.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] RDMA/irdma: Move variable into switch case
Date: Fri, 3 Feb 2023 10:44:09 -0400	[thread overview]
Message-ID: <Y90duSmdXMo4dR85@ziepe.ca> (raw)
In-Reply-To: <Y9ttN4tB1mwB6bSU@unreal>

On Thu, Feb 02, 2023 at 09:58:47AM +0200, Leon Romanovsky wrote:
> On Thu, Feb 02, 2023 at 12:09:50AM +0000, Jack Vogel wrote:
> > Hey Leon,
> > 
> > Oracle switched to GCC11 in our UEK7/OL9 releases recently, leading up to that release we added the ALL_ZERO config option, and then ran into some warnings, our build treats warnings as errors and would fail. For instance this thread: 
> > 
> > https://lkml.iu.edu/hypermail/linux/kernel/2202.1/05558.html
> > 
> > A number of changes were made in the mainline code by Kees Cook and even made it into the linux-5.15.y branch, but a couple of them we have carried as specials for the past year, I was recently prodded about the matter again by an internal group, so I thought I would submit these patches upstream. 
> > 
> > I must apologize though, for unbeknownst to me, our tools team actually back ported the fix from gcc12 regarding these warnings and forgot to tell the UEK group about it :) It wasn’t until you asked about the warnings, I reverted the commits and did a build to capture them, then I discovered they no longer occur. So, sorry about the noise. I will be reverting our own changes as unnecessary now.
> 
> Glad to hear.

Regardless, it is really weird coding style to have a variable
block immediately after the switch statement

Jason

      reply	other threads:[~2023-02-03 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  1:28 [PATCH] RDMA/irdma: Move variable into switch case Jack Vogel
2023-02-01 10:11 ` Leon Romanovsky
2023-02-02  0:09   ` Jack Vogel
2023-02-02  7:58     ` Leon Romanovsky
2023-02-03 14:44       ` Jason Gunthorpe [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=Y90duSmdXMo4dR85@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=jack.vogel@oracle.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mustafa.ismail@intel.com \
    --cc=shiraz.saleem@intel.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 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.