From: Paul Bolle <pebolle@tiscali.nl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Can we drop __must_check from driver_for_each_device()?
Date: Wed, 31 Jul 2013 23:35:13 +0200 [thread overview]
Message-ID: <1375306513.8170.33.camel@x61.thuisdomein> (raw)
Greg,
0) Summary: I think __must_check can be dropped from
driver_for_each_device(). Do you agree?
1) Commit 4a7fb6363f ("add __must_check to device management code")
added __must_check to driver_for_each_device(), seven years ago. But of
the seventeen current users of that function just one actually seems to
care about its return value:
- dead code:
drivers/mtd/onenand/omap2.c:omap2_onenand_rephase()
- callback always returns zero:
drivers/infiniband/hw/qib/qib_init.c:qib_notify_dca()
(see all three possible values of f_notify_dca())
drivers/media/pci/cx25821/cx25821-alsa.c:cx25821_audio_fini()
drivers/media/pci/cx25821/cx25821-alsa.c:cx25821_alsa_init()
drivers/net/can/usb/peak_usb/pcan_usb_core.c:peak_usb_exit()
drivers/net/ethernet/intel/igb/igb_main.c:igb_notify_dca()
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:ixgbe_notify_dca()
drivers/net/ethernet/myricom/myri10ge/myri10ge.c:myri10ge_notify_dca()
- return value of callback ignored:
drivers/iommu/omap-iommu.c:omap_foreach_iommu_device()
(when called by iommu_debugfs_exit())
drivers/isdn/hardware/mISDN/hfcpci.c:hfcpci_softirq()
drivers/media/pci/cx18/cx18-alsa-main.c:cx18_alsa_exit()
drivers/media/pci/ivtv/ivtv-alsa-main.c:ivtv_alsa_exit()
drivers/media/pci/ivtv/ivtvfb.c:ivtvfb_init()
drivers/media/pci/ivtv/ivtvfb.c:ivtvfb_cleanup()
drivers/media/platform/s5p-tv/mixer_video.c:find_and_register_subdev()
drivers/net/wireless/brcm80211/brcmfmac/usb.c:brcmf_usb_exit()
- return value actually used:
drivers/iommu/omap-iommu.c:omap_foreach_iommu_device()
(when called by iommu_debug_init())
2) Please note that if the callback always returns zero,
driver_for_each_device() can still return -EINVAL, but only if it was
provided a NULL "drv" (a struct device_driver). It sure seems odd to do
so. Can that actually happen?
3) So to me it looks the __must_check attribute of
driver_for_each_device() can be dropped. Do you agree?
Paul Bolle
next reply other threads:[~2013-07-31 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 21:35 Paul Bolle [this message]
2013-08-02 0:31 ` Greg Kroah-Hartman
2013-08-06 20:31 ` Paul Bolle
2013-08-07 5:51 ` Greg Kroah-Hartman
2013-08-07 16:57 ` Paul Bolle
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=1375306513.8170.33.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®