Re: [patch 16/17] Immediate Values - Documentation
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
- Date: Thu, 10 Apr 2008 13:33:35 +1000
On Thursday 10 April 2008 01:08:45 Mathieu Desnoyers wrote:
If you have to read the immediate values from a function declared as
__init or __exit, you should explicitly use _imv_read(), which will fall
back on a global variable read. Failing to do so will leave a reference to
the __init section after it is freed (it would generate a modpost
warning).
That's a real usability wart. Couldn't we skip these in the patching loop if
required and revert so noone can make this mistake?
Thanks,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- [RFC PATCH] Immediate Values Support init
- From: Mathieu Desnoyers
- Re: [patch 16/17] Immediate Values - Documentation
- From: Mathieu Desnoyers
- [RFC PATCH] Immediate Values Support init
- References:
- [patch 00/17] Text Edit Lock and Immediate Values for 2.6.25-rc8-mm1
- From: Mathieu Desnoyers
- [patch 16/17] Immediate Values - Documentation
- From: Mathieu Desnoyers
- [patch 00/17] Text Edit Lock and Immediate Values for 2.6.25-rc8-mm1
- Prev by Date: Re: [patch 12/17] Immediate Values - Kconfig menu in EMBEDDED
- Next by Date: Re: [patch 09/17] Add all cpus option to stop machine run
- Previous by thread: [patch 16/17] Immediate Values - Documentation
- Next by thread: Re: [patch 16/17] Immediate Values - Documentation
- Index(es):
Relevant Pages
|