From: Ido Schimmel <idosch@idosch.org>
To: gaoxingwang <gaoxingwang1@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, liaichun@huawei.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, shuah@kernel.org, yanan@huawei.com,
yoshfuji@linux-ipv6.org
Subject: Re: ipv4:the same route is added repeatedly
Date: Wed, 15 Mar 2023 10:54:49 +0200 [thread overview]
Message-ID: <ZBGH2RMEDGCxhctH@shredder> (raw)
In-Reply-To: <20230315074310.2957080-1-gaoxingwang1@huawei.com>
On Wed, Mar 15, 2023 at 03:43:10PM +0800, gaoxingwang wrote:
> Thanks for you reply.This patch works for me.
Thanks for testing.
> Can you submit a patch? Hope the problem will be fixed as soon as possible.
Yes, I will send a patch.
prev parent reply other threads:[~2023-03-15 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 14:41 ipv4:the same route is added repeatedly gaoxingwang
2023-03-14 17:12 ` Ido Schimmel
2023-03-15 7:43 ` gaoxingwang
2023-03-15 8:54 ` Ido Schimmel [this message]
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=ZBGH2RMEDGCxhctH@shredder \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=gaoxingwang1@huawei.com \
--cc=kuba@kernel.org \
--cc=liaichun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=yanan@huawei.com \
--cc=yoshfuji@linux-ipv6.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).