From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Bryan Wu <bryan.wu@analog.com>, Mikael Starvik <starvik@axis.com>,
David Howells <dhowells@redhat.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Roman Zippel <zippel@linux-m68k.org>,
Kyle McMartin <kyle@parisc-linux.org>,
Matthew Wilcox <matthew@wil.cx>, Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] procfs: constify function pointer tables
Date: Tue, 22 Jan 2008 22:25:59 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0801222225320.29273@anakin> (raw)
In-Reply-To: <Pine.LNX.4.64.0801222055440.5722@fbirervta.pbzchgretzou.qr>
On Tue, 22 Jan 2008, Jan Engelhardt wrote:
> This touches so many different places that I did not feel like creating
> a miniscule patch for each architecture. I hope that is ok.
>
> ===Patch begins===
> [PATCH] procfs: constify function pointer tables
>
> Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
> ---
> arch/alpha/kernel/setup.c | 2 +-
> arch/blackfin/kernel/setup.c | 2 +-
> arch/cris/kernel/setup.c | 2 +-
> arch/frv/kernel/setup.c | 2 +-
> arch/h8300/kernel/setup.c | 2 +-
> arch/m32r/kernel/setup.c | 2 +-
> arch/m68k/kernel/setup.c | 2 +-
> arch/m68knommu/kernel/setup.c | 2 +-
> arch/parisc/kernel/setup.c | 2 +-
> arch/ppc/kernel/setup.c | 2 +-
> arch/v850/kernel/procfs.c | 2 +-
> arch/xtensa/kernel/setup.c | 2 +-
> fs/proc/base.c | 6 +++---
> fs/proc/nommu.c | 2 +-
> fs/proc/proc_misc.c | 22 +++++++++++-----------
> fs/proc/proc_sysctl.c | 4 ++--
> fs/proc/proc_tty.c | 2 +-
> fs/proc/task_mmu.c | 8 ++++----
> fs/proc/task_nommu.c | 2 +-
> 19 files changed, 35 insertions(+), 35 deletions(-)
m68k part is:
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-01-22 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54038cd4f87a03884e4f59f8f3697889dfb63c54.1201030614.git.jengelh@computergmbh.de>
2008-01-22 19:51 ` [PATCH] x86: " Jan Engelhardt
2008-01-22 20:56 ` Ingo Molnar
2008-01-22 20:00 ` [PATCH] procfs: " Jan Engelhardt
2008-01-22 21:25 ` Geert Uytterhoeven [this message]
2008-01-22 22:43 ` Mike Frysinger
2008-01-22 23:36 ` Stephen Rothwell
2008-01-23 4:18 ` Bryan Wu
2008-01-23 9:06 ` Jan Engelhardt
2008-01-23 10:41 ` Bryan Wu
2008-01-23 11:25 ` Jan Engelhardt
2008-01-23 12:16 ` Bryan Wu
2008-01-23 16:40 ` Jesper Nilsson
2008-01-22 20:01 ` [PATCH] kernel: constify data and " Jan Engelhardt
2008-01-22 22:57 ` [PATCH] procfs: constify " David Howells
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=Pine.LNX.4.64.0801222225320.29273@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=chris@zankel.net \
--cc=dhowells@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jengelh@computergmbh.de \
--cc=kyle@parisc-linux.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=zippel@linux-m68k.org \
/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
all inboxes | Powered by JetHome®