From: Michael Ellerman <michael@ellerman.id.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, rpjday@crashcourse.ca,
Paul Mackerras <paulus@samba.org>
Subject: Re: [patch 3/4] macintosh: replace deprecated __initcall with device_initcall
Date: Thu, 15 May 2008 16:28:28 +1000 [thread overview]
Message-ID: <1210832908.17568.16.camel@localhost> (raw)
In-Reply-To: <20080514230647.15d58897.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Wed, 2008-05-14 at 23:06 -0700, Andrew Morton wrote:
> On Thu, 15 May 2008 14:14:38 +1000 Paul Mackerras <paulus@samba.org> wrote:
>
> > akpm@linux-foundation.org writes:
> >
> > > -__initcall(adb_init);
> > > +device_initcall(adb_init);
> >
> > There's no particular reason why this needs to go in 2.6.26, is there?
> > It looks to me like something that I should queue up for 2.6.27.
> >
>
> No, this make no difference in code generation - it's just a
> use-the-modern-interface thing.
I missed the memo about __initcall being deprecated, or is it only
deprecated for use in device drivers?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-15 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:12 [patch 3/4] macintosh: replace deprecated __initcall with device_initcall akpm
2008-05-15 4:14 ` Paul Mackerras
2008-05-15 6:06 ` Andrew Morton
2008-05-15 6:28 ` Michael Ellerman [this message]
2008-05-15 6:41 ` Andrew Morton
2008-05-15 9:08 ` Michael Ellerman
2008-05-15 17:43 ` Andrew Morton
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=1210832908.17568.16.camel@localhost \
--to=michael@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rpjday@crashcourse.ca \
/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).