From: Chris Metcalf <cmetcalf@tilera.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Rusty Russell <rusty@rustcorp.com.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] tile: Remove tile-specific _sinitdata and _einitdata
Date: Fri, 29 Aug 2014 16:28:52 -0400 [thread overview]
Message-ID: <5400E284.3020304@tilera.com> (raw)
In-Reply-To: <1409343516-5132-4-git-send-email-geert@linux-m68k.org>
On 8/29/2014 4:18 PM, Geert Uytterhoeven wrote:
> Use standard __init_begin and __init_end instead.
>
> Signed-off-by: Geert Uytterhoeven<geert@linux-m68k.org>
> Acked-by: Chris Metcalf<cmetcalf@tilera.com>
> ---
> arch/tile/include/asm/sections.h | 3 ---
> arch/tile/kernel/vmlinux.lds.S | 2 --
> arch/tile/mm/init.c | 10 +++++-----
> 3 files changed, 5 insertions(+), 10 deletions(-)
This is still in the tile tree; I missed the merge window for 3.17
since I was lazing around on the beach, but I'll push it to Linus
for 3.18.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2014-08-29 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:18 [PATCH 0/4] More section-related cleanups Geert Uytterhoeven
2014-08-29 20:18 ` [PATCH 1/4] frv: Remove unused declarations of __start___ex_table and __stop___ex_table Geert Uytterhoeven
2014-08-29 20:18 ` [PATCH 2/4] ia64: Remove duplicate declarations of __per_cpu_start[] and __per_cpu_end[] Geert Uytterhoeven
2014-08-29 20:18 ` [PATCH 3/4] tile: Remove tile-specific _sinitdata and _einitdata Geert Uytterhoeven
2014-08-29 20:28 ` Chris Metcalf [this message]
2014-08-29 20:18 ` [PATCH 4/4] kernel/param: Consolidate __{start,stop}___param[] in <linux/moduleparam.h> Geert Uytterhoeven
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=5400E284.3020304@tilera.com \
--to=cmetcalf@tilera.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.