From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Corey Minyard <corey@minyard.net>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>
Subject: Re: [PATCH v1 1/1] ipmi: si: Cast to smaller integer type without warning
Date: Wed, 16 Apr 2025 09:34:35 +0300 [thread overview]
Message-ID: <Z_9Pe_l-RrO-9v0u@smile.fi.intel.com> (raw)
In-Reply-To: <Z_6uzH9DsWIh-hIz@mail.minyard.net>
On Tue, Apr 15, 2025 at 02:09:00PM -0500, Corey Minyard wrote:
> On Tue, Apr 15, 2025 at 03:11:56PM +0300, Andy Shevchenko wrote:
> > On Tue, Apr 15, 2025 at 03:06:45PM +0300, Andy Shevchenko wrote:
> > > On Tue, Apr 15, 2025 at 06:39:03AM -0500, Corey Minyard wrote:
> > > > On Tue, Apr 15, 2025 at 11:51:56AM +0300, Andy Shevchenko wrote:
> > > > > Debian clang version 19.1.7 is not happy when compiled with
> > > > > `make W=1` (note, CONFIG_WERROR=y is the default):
> > > > >
> > > > > ipmi_si_platform.c:268:15: error: cast to smaller integer type 'enum si_type' from 'const void *' [-Werror,-Wvoid-pointer-to-enum-cast]
> > > > > 268 | io.si_type = (enum si_type)device_get_match_data(&pdev->dev);
> > > > >
> > > > > Fix this by intermediate cast to the uintptr_t, that makes compiler happy.
> > > >
> > > > Unless things have changed recently, Linus prefers "unsigned long" per
> > > > https://patchwork.kernel.org/project/linux-hardening/patch/20220616143617.449094-1-Jason@zx2c4.com/#24899749
> > >
> > > I'm not sure I got your point. That discussion seems irrelevant to me.
> > > They are talking about pointer-as-an-integer cases. Here we already know
> > > that we are passing integer-as-a-pointer and this is the opposite
> > > conversion.
> > >
> > > > And it would match what is in the match table.
> > >
> > > Match tables are tend to move to pointers, enum is usually goes to int.
> > >
> > > > Is that change ok?
> > >
> > > If you don't like my change, please do yours and consider this as
> > > a bug report that needs to be addressed. I prefer more my solution
> > > as we do that in many places for the exact scenario.
> >
> > Note, the proper solution to the cases like this is to move to info-like
> > structure and actually operate with the pointers instead of enums, longs, etc.
> >
> > That's what's slowly moving on in IIO subsystem, for instance.
>
> Yes, you are right, I'll probably make that change. I'm not sure
> about the uintptr thing, but I think the right change is to do an info
> structure. I never liked that code as it was, anyway.
Please do, I will happily test anything you provide as currently this code breaks
`make W=1` builds.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-04-16 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 8:51 [PATCH v1 1/1] ipmi: si: Cast to smaller integer type without warning Andy Shevchenko
2025-04-15 11:39 ` Corey Minyard
2025-04-15 12:06 ` Andy Shevchenko
2025-04-15 12:11 ` Andy Shevchenko
2025-04-15 19:09 ` Corey Minyard
2025-04-16 6:34 ` Andy Shevchenko [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=Z_9Pe_l-RrO-9v0u@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corey@minyard.net \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=openipmi-developer@lists.sourceforge.net \
/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.