[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110520063419.GA27802@linux-mips.org>
Date: Fri, 20 May 2011 07:34:19 +0100
From: Ralf Baechle <ralf@...ux-mips.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Richard Henderson <rth@...ddle.net>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Matt Turner <mattst88@...il.com>, linux-alpha@...r.kernel.org,
Hirokazu Takata <takata@...ux-m32r.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Roman Zippel <zippel@...ux-m68k.org>,
linux-m68k@...r.kernel.org, Kyle McMartin <kyle@...artin.ca>,
Helge Deller <deller@....de>,
"JamesE.J.Bottomley" <jejb@...isc-linux.org>
Subject: Re: [RFC][PATCH] extable: Make sure all archs define _sdata
On Thu, May 19, 2011 at 09:34:58PM -0400, Steven Rostedt wrote:
> Can I get an Acked-by (or comment) from the following Maintainers:
>
> alpha
> m32r
> m68k
> mips
> parisc
>
> Ingo has discovered that one of my patches broke the builds of these
> architectures. Although he added a quick fix, this patch supplies the
> proper fix and touches the affected architectures. Please review and Ack
> (or NACK with guidance) this patch.
>
> -- Steve
>
> A new utility function is used to determine if a passed in address is
> part of core kernel data or not. It may or may not return true for RO
> data, but this utility must work for RW data. Thus both _sdata and
> _edata must be defined and continuous, without .init sections that may
> later be freed and replaced by volatile memory (memory that can be
> freed).
>
> This utility function is used to determine if data is safe from ever
> being freed. Thus it should return true for all RW global data that is
> not in a module or has been allocated, or false otherwise.
Acked-by: Ralf Baechle <ralf@...ux-mips.org>
Thanks,
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists