All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
Cc: Jonathan Cameron <jic23@kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PULL V2] IIO fixes for v3.7-rc1 set 2 (tiny fixes and regressions only)
Date: Mon, 12 Nov 2012 10:16:46 -0800	[thread overview]
Message-ID: <20121112181646.GA2920@kroah.com> (raw)
In-Reply-To: <50A0BB98.2020802@jic23.retrosnub.co.uk>

On Mon, Nov 12, 2012 at 09:04:24AM +0000, Jonathan Cameron wrote:
> On 12/11/12 02:30, Greg KH wrote:
> >On Sun, Nov 04, 2012 at 04:23:20PM +0000, Jonathan Cameron wrote:
> >>Axel Lin (2):
> >>       iio: hid-sensor: Use __devexit annotation for remove()
> >
> >This one, while maybe nice, sure isn't necessary as CONFIG_HOTPLUG can't
> >be turned off anymore.  So it's not needed for 3.7, right?
> >
> Sorry that patch title doesn't mention why this is done. I should have
> cleaned it up before merging (or poked Axel to do so)
> 
> Right now they are completely incorrectly marked as __devinit rather
> than __devexit.
> 
> Hence if any platform is being clever about ditching init.text after
> module insertion it's not going to be there on removal.

No platform that I know of does this.  And also, __devexit is defined
away as nothing as well due to CONFIG_HOTPLUG always being set.

> If this was simply a case of adding __devexit I'd agree.
> 
> If this annotation still doesn't actually matter I've definitely missed
> something.

It doesn't matter anymore :)

So could we hold off on this one until 3.8?

thanks,

greg k-h

      parent reply	other threads:[~2012-11-12 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04 16:23 [PULL V2] IIO fixes for v3.7-rc1 set 2 (tiny fixes and regressions only) Jonathan Cameron
2012-11-12  2:30 ` Greg KH
2012-11-12  9:04   ` Jonathan Cameron
2012-11-12 14:21     ` Jonathan Cameron
2012-11-12 18:16     ` Greg KH [this message]

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=20121112181646.GA2920@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jic23@jic23.retrosnub.co.uk \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.