public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jiri Slaby" <jirislaby@kernel.org>,
	"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
	"Arnd Bergmann" <arnd@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	"Luis Machado" <luis.machado@arm.com>,
	linux-ide@vger.kernel.org, stable@vger.kernel.org,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Nathan Huckleberry" <nhuck@google.com>
Subject: Re: [PATCH] [v2] ata: ahci: fix enum constants for gcc-13
Date: Wed, 07 Dec 2022 08:32:34 +0100	[thread overview]
Message-ID: <e2597ffc-34d0-470f-87ed-e70d3914956a@app.fastmail.com> (raw)
In-Reply-To: <3beac08e-ffba-8c3b-a5b1-1a34e125b3a7@kernel.org>

On Wed, Dec 7, 2022, at 07:41, Jiri Slaby wrote:
> Arnd,
>
> I just noticed this on stable@. Do you have more of the gcc-13-enum 
> patches? I sent some (this one incl.), but didn't have time for v2 of 
> some of them. So should I respin the rest or have you fixed them all yet?

I only have this one, as this is the only one that Luis asked me
about. I haven't actually tried using gcc-13 myself yet.

>  > [PATCH] ath11k (gcc13): synchronize 
> ath11k_mac_he_gi_to_nl80211_he_gi()'s return type - "Jiri Slaby (SUSE)" 
> <jirislaby@kernel.org> - 2022-10-31 1243.eml:Message-Id: 
> <20221031114341.10377-1-jirislaby@kernel.org>
>  > [PATCH] block_blk-iocost (gcc13): cast enum members to int in prints 
> - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1245.eml:Message-Id: <20221031114520.10518-1-jirislaby@kernel.org>
>  > [PATCH] bonding (gcc13): synchronize bond_{a,t}lb_xmit() types - 
> "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1244.eml:Message-Id: <20221031114409.10417-1-jirislaby@kernel.org>
>  > [PATCH] drm_amd_display (gcc13): fix enum mismatch - "Jiri Slaby 
> (SUSE)" <jirislaby@kernel.org> - 2022-10-31 1242.eml:Message-Id: 
> <20221031114247.10309-1-jirislaby@kernel.org>
>  > [PATCH] drm_nouveau_kms_nv50- (gcc13): fix nv50_wndw_new_ prototype - 
> "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1242.eml:Message-Id: <20221031114229.10289-1-jirislaby@kernel.org>
>  > [PATCH] init: Kconfig (gcc13): disable -Warray-bounds on gcc-13 too - 
> "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1242.eml:Message-Id: <20221031114212.10266-1-jirislaby@kernel.org>
>  > [PATCH] i40e (gcc13): synchronize allocate_free functions return type 
> & values - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1244.eml:Message-Id: <20221031114456.10482-1-jirislaby@kernel.org>
>  > [PATCH] qed (gcc13): use u16 for fid to be big enough - "Jiri Slaby 
> (SUSE)" <jirislaby@kernel.org> - 2022-10-31 1243.eml:Message-Id: 
> <20221031114354.10398-1-jirislaby@kernel.org>
>  > [PATCH] RDMA_srp (gcc13): force int types for max_send_sge and 
> can_queue - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1245.eml:Message-Id: <20221031114506.10501-1-jirislaby@kernel.org>
>  > [PATCH] sfc (gcc13): synchronize ef100_enqueue_skb()'s return type - 
> "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1244.eml:Message-Id: <20221031114440.10461-1-jirislaby@kernel.org>
>  > [PATCH] thunderbolt (gcc13): synchronize tb_port_is_clx_enabled()'s 
> 2nd param - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1243.eml:Message-Id: <20221031114323.10356-1-jirislaby@kernel.org>
>  > [PATCH] wireguard (gcc13): cast enum limits members to int in prints 
> - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1244.eml:Message-Id: <20221031114424.10438-1-jirislaby@kernel.org>
>  > [PATCH 1_2] ata: ahci (gcc13): use BIT() for bit definitions in enum 
> - "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1243.eml:Message-Id: <20221031114310.10337-1-jirislaby@kernel.org>
>  > [PATCH 2_2] ata: ahci (gcc13): use U suffix for enum definitions - 
> "Jiri Slaby (SUSE)" <jirislaby@kernel.org> - 2022-10-31 
> 1243.eml:Message-Id: <20221031114310.10337-2-jirislaby@kernel.org>

I had a look, these all look good to me, as expected. My guess is that
these all only cause a build failure with -Werror, so Luis didn't
get stuck on the warnings.

Some of them appear to overlap with work that Nathan Huckleberry
did a while ago to fix related clang-14 warnings, see e.g.
https://lore.kernel.org/lkml/20220912214523.929094-1-nhuck@google.com/

I don't know what the state of those is.

    Arnd

      reply	other threads:[~2022-12-07  7:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 10:54 [PATCH] [v2] ata: ahci: fix enum constants for gcc-13 Arnd Bergmann
2022-12-05 13:33 ` Damien Le Moal
2022-12-05 13:38   ` Luis Machado
2022-12-05 16:34   ` Luis Machado
2022-12-06  6:46 ` Damien Le Moal
2022-12-07  6:41   ` Jiri Slaby
2022-12-07  7:32     ` Arnd Bergmann [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=e2597ffc-34d0-470f-87ed-e70d3914956a@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.machado@arm.com \
    --cc=nhuck@google.com \
    --cc=rdunlap@infradead.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox