From: Arnd Bergmann <arnd@arndb.de>
To: Bill Pemberton <wfp5p@virginia.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: new warnings from partial __devexit removal
Date: Mon, 26 Nov 2012 20:38:32 +0000 [thread overview]
Message-ID: <201211262038.32276.arnd@arndb.de> (raw)
This is probably known and fixed already, but in case it's not, let me just
mention that I saw two new warnings with ARM allyesconfig about a
__devexit being removed but the __devexit_p() still being there:
drivers/tty/serial/xilinx_uartps.c:1000:12: error: 'xuartps_remove' defined but not used [-Werror=unused-function]
drivers/usb/gadget/mv_udc_core.c:2131:12: error: 'mv_udc_remove' defined but not used [-Werror=unused-function]
Both patches were merged by Greg on Nov 19. I assume that there are a
few more, but I have not checked. These were the only ones that
caused warnings for me.
Arnd
next reply other threads:[~2012-11-26 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 20:38 Arnd Bergmann [this message]
2012-11-26 22:50 ` new warnings from partial __devexit removal gregkh
2012-11-27 9:01 ` Arnd Bergmann
2012-11-27 13:39 ` Bill Pemberton
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=201211262038.32276.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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