All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	jeff.chen_1@oss.nxp.com, linux-wireless@vger.kernel.org,
	briannorris@chromium.org, Jeff Chen <jeff.chen_1@nxp.com>
Subject: Re: [PATCH wireless-next v2 1/2] wifi: mwifiex: append hotfix number to firmware version string
Date: Mon, 19 Oct 2026 16:28:09 +0200	[thread overview]
Message-ID: <20261019142809.GC118352@francesco-nb> (raw)
In-Reply-To: <6b94b803c6424227f6ebc044e0ff2e6b90c180c9.camel@sipsolutions.net>

On Mon, Oct 19, 2026 at 04:16:01PM +0200, Johannes Berg wrote:
> On Mon, 2026-10-19 at 16:13 +0200, Francesco Dolcini wrote:
> > 
> > > +				case FW_HOTFIX_VER_ID: {
> > > +					struct hw_spec_fw_hotfix_ver *hf;
> 
> > > +
> > > +					hf = (void *)tlv;
> > 
> > I would not abuse the void*, you know the type you want
> 
> FWIW, I tend to disagree, spelling out the type again for no real reason
> is just noise. As far as I'm concerned you can do whatever you like in
> the driver though :)

I would say that your opinion trumps mine on this regard.

And it changes nothing on the generated binary, in any way.

The reason I prefer it is that (void*) will silently cast to everything,
and having an explicit type might help in case of mistake introduced
with some future refactoring.

Jeff, up to you, we can take the patch as it is.

And I'd like to have this in the driver, it's something we are missing
and it's valuable.

Francesco


  reply	other threads:[~2026-10-19 14:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 12:36 [PATCH wireless-next v2 0/2] wifi: mwifiex: append hotfix number to firmware version string jeff.chen_1
2026-10-12 12:36 ` [PATCH wireless-next v2 1/2] " jeff.chen_1
2026-10-19 14:13   ` Francesco Dolcini
2026-10-19 14:16     ` Johannes Berg
2026-10-19 14:28       ` Francesco Dolcini [this message]
2026-10-19 14:49         ` Johannes Berg
2026-10-19 15:11           ` Francesco Dolcini
2026-10-12 12:36 ` [PATCH wireless-next v2 2/2] wifi: mwifiex: validate GET_HW_SPEC TLV lengths before parsing jeff.chen_1

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=20261019142809.GC118352@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=briannorris@chromium.org \
    --cc=jeff.chen_1@nxp.com \
    --cc=jeff.chen_1@oss.nxp.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 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.