netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Milan Kocián" <milon@wq.cz>
Cc: David Miller <davem@davemloft.net>,
	akpm@linux-foundation.org, netdev@vger.kernel.org,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 8320] New: replacing route in kernel doesn't send netlink message
Date: Wed, 18 Apr 2007 16:06:28 +0200	[thread overview]
Message-ID: <462625E4.8030802@trash.net> (raw)
In-Reply-To: <1176900487.8348.36.camel@nt.wq.cz>

Milan Kocián wrote:
> On Tue, 2007-04-17 at 14:58 +0200, Patrick McHardy wrote:
> 
>>Milan, could you cook up another patch which uses NLM_F_REPLACE?
> 
> 
> I can try it. Output is in patch below. Review carefully. I don't know
> if it's best approach. It's tested and working without problem
> (probably :-))


Looks good, but your mailer corrupted long lines. Please resend as
attachment and sign off the patch.

> --- net/ipv4.old/fib_hash.c	2007-04-18 12:50:11.000000000 +0200
> +++ net/ipv4/fib_hash.c	2007-04-18 12:39:49.081369320 +0200
> @@ -443,7 +443,6 @@
>  		if (cfg->fc_nlflags & NLM_F_REPLACE) {
>  			struct fib_info *fi_drop;
>  			u8 state;
> -

And please drop this unrelated whitespace change.

> --- net/ipv4.old/fib_semantics.c	2007-04-18 12:50:11.000000000 +0200
> +++ net/ipv4/fib_semantics.c	2007-04-18 12:40:54.807377448 +0200
> @@ -301,7 +301,7 @@
>  }
>  
>  void rtmsg_fib(int event, __be32 key, struct fib_alias *fa,
> -	       int dst_len, u32 tb_id, struct nl_info *info)
> +	       int dst_len, u32 tb_id, struct nl_info *info, unsigned int
> nlm_flags)

This should go on a new line since it exceeds 80 characters.

> --- net/ipv4.old/fib_lookup.h	2007-04-18 12:50:11.000000000 +0200
> +++ net/ipv4/fib_lookup.h	2007-04-18 12:43:42.377902856 +0200
> @@ -30,7 +30,7 @@
>  			 int dst_len, u8 tos, struct fib_info *fi,
>  			 unsigned int);
>  extern void rtmsg_fib(int event, __be32 key, struct fib_alias *fa,
> -		      int dst_len, u32 tb_id, struct nl_info *info);
> +		      int dst_len, u32 tb_id, struct nl_info *info, unsigned int
> nlm_flags);

Same here.

  reply	other threads:[~2007-04-18 14:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200704110937.l3B9b1Kp001053@fire-2.osdl.org>
2007-04-11 16:47 ` [Bugme-new] [Bug 8320] New: replacing route in kernel doesn't send netlink message Andrew Morton
2007-04-11 18:19   ` Patrick McHardy
2007-04-12 17:53     ` Milan Kocián
2007-04-16  4:59       ` Patrick McHardy
2007-04-17  0:10         ` David Miller
2007-04-17 12:58           ` Patrick McHardy
2007-04-18 12:48             ` Milan Kocián
2007-04-18 14:06               ` Patrick McHardy [this message]
2007-04-19 11:30                 ` Milan Kocián
2007-04-19 12:12                   ` Patrick McHardy
2007-04-19 21:42                     ` Andrew Morton
2007-04-20 14:07                       ` [patch 1/1] networking: fix sending netlink message when replace route Milan Kocian

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=462625E4.8030802@trash.net \
    --to=kaber@trash.net \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=davem@davemloft.net \
    --cc=milon@wq.cz \
    --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).