netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH] RTNETLINK: Protocol family wildcard dumping for routing rules
Date: Fri, 8 Apr 2005 00:38:47 +0200	[thread overview]
Message-ID: <20050407223847.GX26731@postel.suug.ch> (raw)
In-Reply-To: <E1DJfBR-0007Ym-00@gondolin.me.apana.org.au>

* Herbert Xu <E1DJfBR-0007Ym-00@gondolin.me.apana.org.au> 2005-04-08 08:09
> Thomas Graf <tgraf@suug.ch> wrote:
> >
> > diff -Nru a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> > --- a/net/core/rtnetlink.c      2005-04-07 23:13:33 +02:00
> > +++ b/net/core/rtnetlink.c      2005-04-07 23:13:33 +02:00
> > @@ -647,7 +647,8 @@
> >        [RTM_GETROUTE - RTM_BASE] = { .dumpit = rtnetlink_dump_all    },
> >        [RTM_NEWNEIGH - RTM_BASE] = { .doit   = neigh_add             },
> >        [RTM_DELNEIGH - RTM_BASE] = { .doit   = neigh_delete          },
> > -       [RTM_GETNEIGH - RTM_BASE] = { .dumpit = neigh_dump_info       }
> > +       [RTM_GETNEIGH - RTM_BASE] = { .dumpit = neigh_dump_info       },
> > +       [RTM_GETRULE  - RTM_BASE] = { .dumpit = rtnetlink_dump_all    }
> > };
> 
> Just a trivial comment.  How about adding a comma at the end of the last
> entry so that the next patch won't have to touch it?

Sure, bk fix'ed and new patch attached. However, I haven't read all
the recent happenings around bk and somewhat missed rc2. I just noticed
the freeze so not sure if this still makes sense.

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2005/04/08 00:24:50+02:00 tgraf@suug.ch 
#   [RTNETLINK]: Protocol family wildcard dumping for routing rules
#   
#   Be kind to userspace and don't force them to hardcode protocol
#   families just to have it changed again once we support routing
#   rules for more than one protocol family.
#   
#   Signed-off-by: Thomas Graf <tgraf@suug.ch>
#   Signed-off-by: David S. Miller <davem@davemloft.net>
# 
# net/core/rtnetlink.c
#   2005/04/08 00:24:40+02:00 tgraf@suug.ch +2 -1
#   [RTNETLINK]: Protocol family wildcard dumping for routing rules
# 
diff -Nru a/net/core/rtnetlink.c b/net/core/rtnetlink.c
--- a/net/core/rtnetlink.c	2005-04-08 00:35:37 +02:00
+++ b/net/core/rtnetlink.c	2005-04-08 00:35:37 +02:00
@@ -647,7 +647,8 @@
 	[RTM_GETROUTE - RTM_BASE] = { .dumpit = rtnetlink_dump_all    },
 	[RTM_NEWNEIGH - RTM_BASE] = { .doit   = neigh_add	      },
 	[RTM_DELNEIGH - RTM_BASE] = { .doit   = neigh_delete	      },
-	[RTM_GETNEIGH - RTM_BASE] = { .dumpit = neigh_dump_info	      }
+	[RTM_GETNEIGH - RTM_BASE] = { .dumpit = neigh_dump_info	      },
+	[RTM_GETRULE  - RTM_BASE] = { .dumpit = rtnetlink_dump_all    },
 };
 
 static int rtnetlink_event(struct notifier_block *this, unsigned long event, void *ptr)

  reply	other threads:[~2005-04-07 22:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07 21:38 [PATCH] RTNETLINK: Protocol family wildcard dumping for routing rules Thomas Graf
2005-04-07 22:09 ` Herbert Xu
2005-04-07 22:38   ` Thomas Graf [this message]
2005-04-07 23:13     ` jamal
2005-04-07 23:24       ` Thomas Graf
2005-04-08  0:48         ` jamal
2005-04-08  1:04           ` Thomas Graf
2005-04-08  1:11             ` jamal

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=20050407223847.GX26731@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.com \
    /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).