From: "Mike Frysinger" <vapier.adi@gmail.com>
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>,
"Geert Uytterhoeven" <geert@linux-m68k.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 17:43:13 -0500 [thread overview]
Message-ID: <8bd0f97a0801221443k1442046br4d6a6c8e1be7e666@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801222055440.5722@fbirervta.pbzchgretzou.qr>
On Jan 22, 2008 3:00 PM, Jan Engelhardt <jengelh@computergmbh.de> 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.
there is a linux-arch alias so you dont have to look up every
maintainer yourself ;)
> arch/blackfin/kernel/setup.c | 2 +-
Blackfin changes look fine, thanks
Acked-by: Mike Frysinger <vapier@gentoo.org>
-mike
next prev parent reply other threads:[~2008-01-22 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54038cd4f87a03884e4f59f8f3697889dfb63c54.1201030614.git.jengelh@computergmbh.de>
2008-01-22 20:00 ` [PATCH] procfs: constify function pointer tables Jan Engelhardt
2008-01-22 21:25 ` Geert Uytterhoeven
2008-01-22 22:43 ` Mike Frysinger [this message]
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 22:57 ` 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=8bd0f97a0801221443k1442046br4d6a6c8e1be7e666@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=chris@zankel.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--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;
as well as URLs for NNTP newsgroup(s).