[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZRwZIXaVS4yxGSQF@kernel.org>
Date: Tue, 3 Oct 2023 15:37:37 +0200
From: Simon Horman <horms@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, vadfed@...com, arkadiusz.kubalewski@...el.com,
jiri@...nulli.us, netdev@...r.kernel.org, llvm@...ts.linux.dev,
patches@...ts.linux.dev, richardcochran@...il.com,
jonathan.lemon@...il.com, saeedm@...dia.com, leon@...nel.org,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix a couple recent instances of
-Wincompatible-function-pointer-types-strict from ->mode_get()
implementations
On Mon, Oct 02, 2023 at 01:55:19PM -0700, Nathan Chancellor wrote:
> Hi all,
>
> This series fixes a couple of instances of
> -Wincompatible-function-pointer-types-strict that were introduced by a
> recent series that added a new type of ops, struct dpll_device_ops,
> along with implementations of the callback ->mode_get() that had a
> mismatched mode type.
>
> This warning is not currently enabled for any build but I am planning on
> submitting a patch to add it to W=1 to prevent new instances of the
> warning from popping up while we try and fix the existing instances in
> other drivers.
>
> This series is based on current net-next but if they need to go into
> individual maintainer trees, please feel free to take the patches
> individually.
>
> Cheers,
> Nathan
>
> ---
> Nathan Chancellor (2):
> ptp: Fix type of mode parameter in ptp_ocp_dpll_mode_get()
> mlx5: Fix type of mode parameter in mlx5_dpll_device_mode_get()
For series,
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists