From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@linux-foundation.org>,
acme@ghostprotocols.net, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org, dccp@vger.kernel.org,
netdev@vger.kernel.org
Subject: [-mm patch] make struct dccp_li_cachep static
Date: Sun, 1 Jul 2007 22:23:44 +0200 [thread overview]
Message-ID: <20070701202344.GX10869@stusta.de> (raw)
In-Reply-To: <20070628034321.38c9f12b.akpm@linux-foundation.org>
On Thu, Jun 28, 2007 at 03:43:21AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.22-rc4-mm2:
>...
> git-net.patch
>...
> git trees
>...
Struct dccp_li_cachep can become static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
--- linux-2.6.22-rc6-mm1/net/dccp/ccids/lib/loss_interval.c.old 2007-07-01 00:38:12.000000000 +0200
+++ linux-2.6.22-rc6-mm1/net/dccp/ccids/lib/loss_interval.c 2007-07-01 00:38:21.000000000 +0200
@@ -27,7 +27,7 @@
u32 dccplih_interval;
};
-struct kmem_cache *dccp_li_cachep __read_mostly;
+static struct kmem_cache *dccp_li_cachep __read_mostly;
static inline struct dccp_li_hist_entry *dccp_li_hist_entry_new(const gfp_t prio)
{
parent reply other threads:[~2007-07-01 20:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070628034321.38c9f12b.akpm@linux-foundation.org>]
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=20070701202344.GX10869@stusta.de \
--to=bunk@stusta.de \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).