From: Bill Pemberton <wfp5p@virginia.edu>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH 028/493] video: hpfb: remove use of __devexit_p
Date: Mon, 19 Nov 2012 18:19:37 +0000 [thread overview]
Message-ID: <1353349642-3677-28-git-send-email-wfp5p@virginia.edu> (raw)
CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed, remove it.
Also fix the indentation for the initialization of the
hpfb_driver struct to make chkpatch happy.
Signed-off-by: Bill Pemberton <wfp5p@virginia.edu>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: linux-fbdev@vger.kernel.org
---
drivers/video/hpfb.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/video/hpfb.c b/drivers/video/hpfb.c
index 7324865..1f15523 100644
--- a/drivers/video/hpfb.c
+++ b/drivers/video/hpfb.c
@@ -370,10 +370,10 @@ static struct dio_device_id hpfb_dio_tbl[] = {
};
static struct dio_driver hpfb_driver = {
- .name = "hpfb",
- .id_table = hpfb_dio_tbl,
- .probe = hpfb_dio_probe,
- .remove = __devexit_p(hpfb_remove_one),
+ .name = "hpfb",
+ .id_table = hpfb_dio_tbl,
+ .probe = hpfb_dio_probe,
+ .remove = hpfb_remove_one,
};
int __init hpfb_init(void)
--
1.8.0
reply other threads:[~2012-11-19 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1353349642-3677-28-git-send-email-wfp5p@virginia.edu \
--to=wfp5p@virginia.edu \
--cc=linux-fbdev@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