From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: Bill Pemberton <wfp5p-4Ng6DfrEGID2fBVCVOL8/A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 407/493] infiniband: remove use of __devexit
Date: Mon, 19 Nov 2012 16:17:24 -0700 [thread overview]
Message-ID: <20121119231724.GA27526@obsidianresearch.com> (raw)
In-Reply-To: <20121119230006.GA2523-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
On Mon, Nov 19, 2012 at 03:00:06PM -0800, Greg KH wrote:
> I could just leave things alone, with CONFIG_HOTPLUG always enabled, but
> then people will continue to blindly use the __dev* markings, getting it
> wrong at times, but never realizing that they don't do anything anymore.
Well, I was thinking more along the lines of leaving the capability to
remove the __dev* marked functions from the link, as is today,
independent of the other stuff CONFIG_HOTPLUG controls. But reviewing
your comments from the archive makes me think a motivation is misuse
of the __dev* markings..
Thanks for the insight,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-11-19 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353349642-3677-1-git-send-email-wfp5p@virginia.edu>
[not found] ` <1353349642-3677-1-git-send-email-wfp5p-4Ng6DfrEGID2fBVCVOL8/A@public.gmane.org>
2012-11-19 18:20 ` [PATCH 068/493] infiniband: remove use of __devexit_p Bill Pemberton
2012-11-19 18:22 ` [PATCH 210/493] infiniband: remove use of __devinit Bill Pemberton
2012-11-19 18:24 ` [PATCH 308/493] infiniband: remove use of __devinitdata Bill Pemberton
2012-11-19 18:25 ` [PATCH 407/493] infiniband: remove use of __devexit Bill Pemberton
[not found] ` <1353349642-3677-407-git-send-email-wfp5p-4Ng6DfrEGID2fBVCVOL8/A@public.gmane.org>
2012-11-19 20:09 ` Jason Gunthorpe
[not found] ` <20121119200921.GD1556-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-11-19 20:19 ` Greg KH
[not found] ` <20121119201938.GA5614-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-11-19 21:49 ` Jason Gunthorpe
[not found] ` <20121119214922.GA5636-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-11-19 22:06 ` Greg KH
[not found] ` <20121119220632.GA1946-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-11-19 22:48 ` Jason Gunthorpe
[not found] ` <20121119224845.GB5636-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-11-19 23:00 ` Greg KH
[not found] ` <20121119230006.GA2523-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-11-19 23:17 ` Jason Gunthorpe [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=20121119231724.GA27526@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wfp5p-4Ng6DfrEGID2fBVCVOL8/A@public.gmane.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