netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: davem@davemloft.net, kaber@trash.net, sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, Eric Leblond <eric@inl.fr>
Subject: [PATCH 3/3] netfilter: fix nf_logger name in ebt_ulog.
Date: Thu, 26 Mar 2009 08:59:56 +0100	[thread overview]
Message-ID: <1238054396-9088-3-git-send-email-eric@inl.fr> (raw)
In-Reply-To: <1238053819.13879.4.camel@ice-age>

This patch renames the ebt_ulog nf_logger from "ulog" to "ebt_ulog" to
be in sync with other modules naming. As this name was currently only
used for informational purpose, the renaming should be harmless.

Signed-off-by: Eric Leblond <eric@inl.fr>
---
 net/bridge/netfilter/ebt_ulog.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/net/bridge/netfilter/ebt_ulog.c b/net/bridge/netfilter/ebt_ulog.c
index ac6fa43..133eeae 100644
--- a/net/bridge/netfilter/ebt_ulog.c
+++ b/net/bridge/netfilter/ebt_ulog.c
@@ -280,7 +280,7 @@ static struct xt_target ebt_ulog_tg_reg __read_mostly = {
 };
 
 static struct nf_logger ebt_ulog_logger __read_mostly = {
-	.name		= "ulog",
+	.name		= "ebt_ulog",
 	.logfn		= &ebt_log_packet,
 	.me		= THIS_MODULE,
 };
-- 
1.5.6.3


  parent reply	other threads:[~2009-03-26  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  6:37 linux-next: net tree build warnings Stephen Rothwell
2009-03-26  7:50 ` Eric Leblond
2009-03-26  7:59   ` [PATCH 1/3] netfilter: fix warning about invalid const usage Eric Leblond
2009-03-26  8:03     ` David Miller
2009-03-26  7:59   ` [PATCH 2/3] netfilter: fix warning in ebt_ulog init function Eric Leblond
2009-03-26  8:04     ` David Miller
2009-03-26  7:59   ` Eric Leblond [this message]
2009-03-26  8:04     ` [PATCH 3/3] netfilter: fix nf_logger name in ebt_ulog David Miller
2009-03-26 13:17   ` linux-next: net tree build warnings Patrick McHardy
2009-03-26 22:01   ` Stephen Rothwell

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=1238054396-9088-3-git-send-email-eric@inl.fr \
    --to=eric@inl.fr \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).