LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Marc Pignat" <marc.pignat@hevs.ch>,
wim@iguana.be, linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH] watchdog on gpio
Date: Mon, 14 Jan 2008 09:29:05 +0000 [thread overview]
Message-ID: <20080114092905.227c5a38@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <8bd0f97a0801140128i2ebf9236uabe0e0b8cf15fbe@mail.gmail.com>
> > Saves memory - you can't make inlined strings __initdata without breaking
> > some compilers. So it is correct.
>
> you could make the same argument about all strings used in all __init
> functions. making a special case for this one string is just
> confusing. this is also used from the *platfrom driver probe*
> function, not the *module init* function, which means it should be
> __devinitdata (see below) ... which quickly adds to the
> confusion/craziness.
Not neccessarily see below. For strings there is a tricky tradeoff
between space on embedded boxes and simplicity. On a 2GB desktop PC the
decision is fairly trivial, on a PDA it gets a bit more important.
> > > > +static int __init gpio_wdt_probe(struct platform_device *pdev)
> > >
> > > shouldnt this be __devinit ?
> >
> > IFF the device can be found/removed dynamically.
>
> wont __init get freed once the module has finished loading ?
If your platform creates the device statically (as a lot of embedded
platforms do) then the __init is fine. The platform register in
init_module will call back the driver probe method and attach the device
before the init_module exits.
Alan
next prev parent reply other threads:[~2008-01-14 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 15:11 Marc Pignat
2008-01-10 17:14 ` Ben Dooks
2008-01-11 16:40 ` Florian Fainelli
2008-01-14 7:34 ` Marc Pignat
2008-01-14 8:08 ` Mike Frysinger
2008-01-14 8:04 ` Mike Frysinger
2008-01-14 9:03 ` Alan Cox
2008-01-14 9:28 ` Mike Frysinger
2008-01-14 9:29 ` Alan Cox [this message]
2008-01-14 9:45 ` Mike Frysinger
2008-01-14 12:14 ` Haavard Skinnemoen
2008-01-14 12:22 ` Mike Frysinger
2008-01-14 13:30 ` Haavard Skinnemoen
2008-01-14 12:49 ` Johannes Weiner
2008-01-14 13:03 ` Mike Frysinger
2008-01-14 13:56 ` printk-wrapper with sectionized string constants [was: Re: [RFC, PATCH] watchdog on gpio] Johannes Weiner
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=20080114092905.227c5a38@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--cc=vapier.adi@gmail.com \
--cc=wim@iguana.be \
--subject='Re: [RFC, PATCH] watchdog on gpio' \
/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
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).