linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: linux-kernel@vger.kernel.org
Subject: wrong usage of __devexit_p and __exit_p
Date: Mon, 12 Jan 2009 14:50:57 +0100	[thread overview]
Message-ID: <20090112135057.GA10250@pengutronix.de> (raw)

Hello,

I found several drivers that use __devexit_p and __exit_p on functions
that don't live in .devexit.text or .exit.text resp.

The impact is either that these functions use memory without being used
or that they don't link.

I send 24 patches as a reply to this mail.  I choosed to move the
functions into the respective function instead of using the right
__{dev,}exit_p wrapper because it seems to me to have less impact.

I didn't made the effort to find out the right people to Cc: but I hope
that Andrew takes care of that :-)

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

             reply	other threads:[~2009-01-12 13:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 13:50 Uwe Kleine-König [this message]
2009-01-12 13:52 ` [PATCH] move asic3_remove to .devexit.text Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move bbc_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move grover_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move hifn_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move ilo_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move jsm_remove_one " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move max7301_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move megaraid_detach_one " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move mpc85xx_pci_err_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move mv64x60_pci_err_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move mxcnd_remove to .exit.text Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move pxa_camera_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move s3c_adc_remove to .devexit.text Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move s3c_pwm_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move sc26xx_driver_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move spidev_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move stex_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move stli_pciremove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move vhci_hcd_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move virtballoon_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move virtblk_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move virtnet_remove " Uwe Kleine-König
2009-01-12 13:52 ` [PATCH] move virtrng_remove " Uwe Kleine-König
2009-01-12 14:14 ` wrong usage of __devexit_p and __exit_p Sam Ravnborg
2009-01-12 14:43   ` Uwe Kleine-König
2009-01-12 20:55     ` Uwe Kleine-König
2009-01-12 21:21       ` Sam Ravnborg
2009-01-12 22:15         ` Uwe Kleine-König
2009-01-13  5:37           ` Sam Ravnborg
2009-01-13 20:54             ` Uwe Kleine-König

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=20090112135057.GA10250@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).