linux-kernel - drivers/isdn/hardware/mISDN/hfcpci.c compiler warning seems like a BUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1247639997.2437.21.camel@ht.satnam>
Date:	Wed, 15 Jul 2009 12:09:57 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Matthias Urlichs <matthias@...ichs.de>,
	Karsten Keil <kkeil@...e.de>, isdn@...ux-pingi.de,
	LKML <linux-kernel@...r.kernel.org>
Subject: drivers/isdn/hardware/mISDN/hfcpci.c compiler warning seems like a
 BUG

I am getting this compiler warning in linus tree :

  CC [M]  drivers/isdn/hardware/mISDN/hfcpci.o
drivers/isdn/hardware/mISDN/hfcpci.c: In function ‘hfcpci_softirq’:
drivers/isdn/hardware/mISDN/hfcpci.c:2333: warning: ignoring return value of ‘driver_for_each_device’, declared with attribute warn_unused_result

static void
hfcpci_softirq(void *arg)
{
        (void) driver_for_each_device(&hfc_driver.driver, NULL, arg,
                                        _hfcpci_softirq);

        /* if next event would be in the past ... */
        if ((s32)(hfc_jiffies + tics - jiffies) <= 0)
                hfc_jiffies = jiffies + 1;
        else
                hfc_jiffies += tics;
        hfc_tl.expires = hfc_jiffies;
        add_timer(&hfc_tl);
}

It seems to me it should return is driver_for_each_device fails :
        if (driver_for_each_device(&hfc_driver.driver, NULL, arg,
                                   _hfcpci_softirq))
		return;

or if possible can we return this error code for hfcpci_softirq()

Thanks,
--
JSR


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/