From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Bill Pemberton" <wfp5p@virginia.edu>,
gregkh@linuxfoundation.org,
"Tomasz Stanislawski" <t.stanislaws@samsung.com>,
"Kamil Debski" <k.debski@samsung.com>,
"Maxim Levitsky" <maximlevitsky@gmail.com>,
"Heungjun Kim" <riverful.kim@samsung.com>,
"David Härdeman" <david@hardeman.nu>,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
"Jeongtae Park" <jtp.park@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
mjpeg-users@lists.sourceforge.net,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Guennadi Liakhovetski" <g.liakhovetski@gmx.de>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 133/493] remove use of __devexit_p
Date: Thu, 3 Jan 2013 16:33:24 +0000 [thread overview]
Message-ID: <201301031633.24214.arnd@arndb.de> (raw)
In-Reply-To: <1353349642-3677-133-git-send-email-wfp5p@virginia.edu>
On Monday 19 November 2012, Bill Pemberton wrote:
> CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
> needed.
I've seen a few cases where __devexit was incorrectly paired with __exit_p().
Have you checked for those as well? It may be worth removing those at the
same time.
Arnd
next prev parent reply other threads:[~2013-01-03 16:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353349642-3677-1-git-send-email-wfp5p@virginia.edu>
2012-11-19 18:19 ` [PATCH 027/493] media: remove use of __devexit_p in bt878.c Bill Pemberton
2012-11-19 18:19 ` [PATCH 031/493] docbook: remove references to __devexit_p Bill Pemberton
2012-11-19 18:20 ` [PATCH 103/493] staging: dt3155v4l: remove use of __devexit_p Bill Pemberton
2012-11-19 18:20 ` [PATCH 104/493] staging: lirc: " Bill Pemberton
2012-11-19 18:21 ` [PATCH 133/493] " Bill Pemberton
2012-11-21 12:10 ` Guennadi Liakhovetski
2012-11-22 10:36 ` Laurent Pinchart
2012-11-22 11:20 ` Prabhakar Lad
2013-01-03 11:43 ` Guennadi Liakhovetski
2013-01-03 16:39 ` Greg KH
2013-01-03 16:33 ` Arnd Bergmann [this message]
2012-11-19 18:22 ` [PATCH 186/493] staging: lirc: remove use of __devinit Bill Pemberton
2012-11-19 18:22 ` [PATCH 187/493] staging: solo6x10: " Bill Pemberton
2012-11-19 18:22 ` [PATCH 188/493] staging: dt3155v4l: " Bill Pemberton
2012-11-19 18:23 ` [PATCH 234/493] media: " Bill Pemberton
2012-11-22 22:55 ` Guennadi Liakhovetski
2012-12-06 7:54 ` Prabhakar Lad
2012-11-19 18:23 ` [PATCH 289/493] docbook: remove discussion " Bill Pemberton
2012-11-19 18:24 ` [PATCH 332/493] media: remove use of __devinitdata Bill Pemberton
2012-11-19 18:25 ` [PATCH 375/493] media: remove use of __devinitconst Bill Pemberton
2012-11-19 18:26 ` [PATCH 444/493] media: remove use of __devexit Bill Pemberton
2012-11-23 7:45 ` Guennadi Liakhovetski
2012-12-06 7:51 ` Prabhakar Lad
2012-11-19 18:27 ` [PATCH 481/493] staging: lirc: " Bill Pemberton
2012-11-19 18:27 ` [PATCH 482/493] staging: dt3155v4l: " Bill Pemberton
2012-11-19 18:27 ` [PATCH 483/493] staging: solo6x10: " Bill Pemberton
2012-11-19 18:27 ` [PATCH 493/493] docbook: " 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=201301031633.24214.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=david@hardeman.nu \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jtp.park@samsung.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=mchehab@infradead.org \
--cc=mjpeg-users@lists.sourceforge.net \
--cc=riverful.kim@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=t.stanislaws@samsung.com \
--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