From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
andi@firstfloor.org, clameter@sgi.com, a.p.zijlstra@chello.nl
Subject: Re: [PATCH] slub: /proc/slabinfo ABI compatibility
Date: Sat, 22 Dec 2007 14:40:10 +0100 [thread overview]
Message-ID: <20071222134010.GA12294@elte.hu> (raw)
In-Reply-To: <84144f020712220531x238da99bi19ff06aaddfc5fc3@mail.gmail.com>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Hi Ingo,
>
> On Dec 22, 2007 3:14 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > Also please apply the cleanup patch below, it fixes 34 checkpatch errors
> > and warnings in mm/slub.c.
>
> Those are already fixed in -mm:
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc5/2.6.24-rc5-mm1/broken-out/slub-fix-coding-style-violations.patch
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc5/2.6.24-rc5-mm1/broken-out/slub-fix-coding-style-violations-checkpatch-fixes.patch
ah, didnt see that. Could you pick up bits of my patch because it seems
to do a better job, such as proper c99 initializer:
+static struct notifier_block __cpuinitdata slab_notifier = {
+ .notifier_call = slab_cpuup_callback
+};
instead of your:
+static struct notifier_block __cpuinitdata slab_notifier = {
+ &slab_cpuup_callback, NULL, 0
+};
also, my patch fixes all the warnings as well, not just the errors. So
please give it a second look ;-)
Ingo
next prev parent reply other threads:[~2007-12-22 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 12:47 Pekka J Enberg
2007-12-22 13:14 ` Ingo Molnar
2007-12-22 13:31 ` Pekka Enberg
2007-12-22 13:40 ` Ingo Molnar [this message]
2007-12-22 13:49 ` Pekka Enberg
2007-12-22 13:16 ` Ingo Molnar
2007-12-22 13:37 ` Ingo Molnar
2007-12-22 13:42 ` Pekka Enberg
2007-12-24 19:12 ` Christoph Lameter
2007-12-24 20:59 ` Pekka Enberg
2007-12-26 21:28 ` Christoph Lameter
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=20071222134010.GA12294@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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®