From: Adrian Bunk <bunk@stusta.de>
To: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>
Subject: [PATCH] uninline __sigqueue_alloc (fwd)
Date: Fri, 29 Oct 2004 23:47:23 +0200 [thread overview]
Message-ID: <20041029214723.GX6677@stusta.de> (raw)
The patch forwarded below still applies against 2.6.10-rc1-mm2.
Was there any specific reason why it wasn't applied?
----- Forwarded message from Chris Wright <chrisw@osdl.org> -----
Date: Fri, 22 Oct 2004 14:35:51 -0700
From: Chris Wright <chrisw@osdl.org>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] uninline __sigqueue_alloc
Christoph suggests letting the compiler choose. No real compelling reason
to inline anyhow. I had some vmlinux size numbers suggesting inline was
better, but re-running them on newer kernel is giving different results,
favoring uninline. Best let compiler choose. Un-inline __sigqueue_alloc.
Signed-off-by: Chris Wright <chrisw@osdl.org>
===== kernel/signal.c 1.140 vs edited =====
--- 1.140/kernel/signal.c 2004-10-21 13:46:54 -07:00
+++ edited/kernel/signal.c 2004-10-22 14:00:00 -07:00
@@ -265,7 +265,7 @@
return sig;
}
-static inline struct sigqueue *__sigqueue_alloc(struct task_struct *t, int flags)
+static struct sigqueue *__sigqueue_alloc(struct task_struct *t, int flags)
{
struct sigqueue *q = NULL;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
reply other threads:[~2004-10-29 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041029214723.GX6677@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.