public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Tim Abbott <tabbott@ksplice.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v2 2/5] Use new __init_task_data macro in arch init_task.c files.
Date: Wed, 9 Sep 2009 11:55:06 +0900	[thread overview]
Message-ID: <20090909025506.GB23049@linux-sh.org> (raw)
In-Reply-To: <1252464546-26394-3-git-send-email-tabbott@ksplice.com>

On Tue, Sep 08, 2009 at 10:49:03PM -0400, Tim Abbott wrote:
> From: Joe Perches <joe@perches.com>
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> Signed-off-by: Tim Abbott <tabbott@ksplice.com>
> 
> ---
>  arch/arm/kernel/init_task.c            |    5 ++---
>  arch/avr32/kernel/init_task.c          |    5 ++---
>  arch/cris/kernel/process.c             |    5 ++---
>  arch/frv/kernel/init_task.c            |    5 ++---
>  arch/h8300/kernel/init_task.c          |    5 ++---
>  arch/ia64/kernel/init_task.c           |    3 ++-
>  arch/m32r/kernel/init_task.c           |    5 ++---
>  arch/m68k/kernel/process.c             |    6 +++---
>  arch/m68knommu/kernel/init_task.c      |    5 ++---
>  arch/microblaze/kernel/init_task.c     |    5 ++---
>  arch/mips/kernel/init_task.c           |    5 ++---
>  arch/mn10300/kernel/init_task.c        |    5 ++---
>  arch/parisc/kernel/init_task.c         |    4 ++--
>  arch/powerpc/kernel/init_task.c        |    5 ++---
>  arch/powerpc/kernel/machine_kexec_64.c |    5 +++--
>  arch/s390/kernel/init_task.c           |    5 ++---
>  arch/sh/kernel/init_task.c             |    5 ++---
>  arch/sparc/kernel/init_task.c          |    5 ++---
>  arch/um/kernel/init_task.c             |    5 ++---
>  arch/x86/kernel/init_task.c            |    5 ++---
>  arch/xtensa/kernel/init_task.c         |    5 ++---
>  21 files changed, 44 insertions(+), 59 deletions(-)
> 
Acked-by: Paul Mundt <lethal@linux-sh.org>

  reply	other threads:[~2009-09-09  2:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  2:49 [PATCH v2 0/5] Use macros rather than hardcoding section names Tim Abbott
2009-09-09  2:49 ` [PATCH v2 1/5] kbuild: Don't define ALIGN and ENTRY when preprocessing linker scripts Tim Abbott
2009-09-09  2:49 ` [PATCH v2 2/5] Use new __init_task_data macro in arch init_task.c files Tim Abbott
2009-09-09  2:55   ` Paul Mundt [this message]
2009-09-09  2:58   ` Daniel Walker
2009-09-09  3:03     ` Joe Perches
2009-09-09  3:07       ` Daniel Walker
2009-09-09  3:10         ` Joe Perches
2009-09-09  3:21           ` Daniel Walker
2009-09-09  3:31             ` Joe Perches
2009-09-09  3:44               ` Daniel Walker
2009-09-09  3:49                 ` Joe Perches
2009-09-09  3:32             ` Paul Mundt
2009-09-09  4:11               ` Dmitry Torokhov
2009-09-09  2:49 ` [PATCH v2 3/5] Use macros for .bss.page_aligned section Tim Abbott
2009-09-09  2:54   ` Paul Mundt
2009-09-09  2:49 ` [PATCH v2 4/5] powerpc: remove unused __page_aligned definition Tim Abbott
2009-09-11  7:33   ` Benjamin Herrenschmidt
2009-09-09  2:49 ` [PATCH v2 5/5] Use macros for .data.page_aligned section Tim Abbott

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=20090909025506.GB23049@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tabbott@ksplice.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox