Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: daire.mcnamara@microchip.com
Cc: conor.dooley@microchip.com, lpieralisi@kernel.org,
	robh@kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-riscv@lists.infradead.org, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v1 2/8] PCI: microchip: Remove cast warning for devm_add_action_or_reset() arg
Date: Sun, 25 Jun 2023 03:34:28 +0900	[thread overview]
Message-ID: <20230624183428.GF2636347@rocinante> (raw)
In-Reply-To: <20230614155556.4095526-3-daire.mcnamara@microchip.com>

[+CC Simon]

Hello,

> The kernel test robot reported that the ugly cast from
> void(*)(struct clk *) to void (*)(void *) converts to incompatible
> function type.  This commit adopts the common convention of creating a
> trivial stub function that takes a void * and passes it to the
> underlying function that expects the more specific type.

This is a nice change, but it seems it has been carried along a few other
series and through their different revisions.  Simon also found the problem
and addressed it independently per:

  https://lore.kernel.org/linux-pci/20230511-pci-microchip-clk-cast-v1-1-7674f4d4e218@kernel.org

However, we have a few other drivers where we could take care of this, per:

drivers/pci/controller/pcie-microchip-host.c
864-		return ERR_PTR(ret);
865-
866:	devm_add_action_or_reset(dev, (void (*) (void *))clk_disable_unprepare,
867-				 clk);
868-

drivers/pci/controller/dwc/pcie-keembay.c
170-
171-	ret = devm_add_action_or_reset(dev,
172:				       (void(*)(void *))clk_disable_unprepare,
173-				       clk);
174-	if (ret)

drivers/pci/controller/dwc/pci-meson.c
189-
190-	devm_add_action_or_reset(dev,
191:				 (void (*) (void *))clk_disable_unprepare,
192-				 clk);
193-

If neither you nor Simon has objections, I can send a small series to
address these in a single take.  You could then drop this particular patch
from v2 of this series, should you send a second revision at some point.

Thoughts?

	Krzysztof

  reply	other threads:[~2023-06-24 18:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 15:55 [PATCH v1 0/8] PCI: microchip: Fixes and clean-ups daire.mcnamara
2023-06-14 15:55 ` [PATCH v1 1/8] PCI: microchip: Correct the DED and SEC interrupt bit offsets daire.mcnamara
2023-06-14 15:55 ` [PATCH v1 2/8] PCI: microchip: Remove cast warning for devm_add_action_or_reset() arg daire.mcnamara
2023-06-24 18:34   ` Krzysztof Wilczyński [this message]
2023-06-24 19:03     ` Simon Horman
2023-06-14 15:55 ` [PATCH v1 3/8] PCI: microchip: enable building this driver as a module daire.mcnamara
2023-06-14 19:53   ` Uwe Kleine-König
2023-06-19 10:00   ` Lorenzo Pieralisi
2023-06-14 15:55 ` [PATCH v1 4/8] PCI: microchip: Align register, offset, and mask names with hw docs daire.mcnamara
2023-06-14 15:55 ` [PATCH v1 5/8] PCI: microchip: Enable event handlers to access bridge and ctrl ptrs daire.mcnamara
2023-06-14 15:55 ` [PATCH v1 6/8] PCI: microchip: Clean up initialisation of interrupts daire.mcnamara
2023-06-14 15:55 ` [PATCH v1 7/8] PCI: microchip: Gather MSI information from hardware config registers daire.mcnamara
2023-06-19 10:20   ` Lorenzo Pieralisi
2023-06-14 15:55 ` [PATCH v1 8/8] PCI: microchip: Re-partition code between probe() and init() daire.mcnamara

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=20230624183428.GF2636347@rocinante \
    --to=kw@linux.com \
    --cc=bhelgaas@google.com \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=horms@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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