From: David Ahern <dsahern@kernel.org>
To: williamsukatube@163.com, davem@davemloft.net,
yoshfuji@linux-ipv6.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] nexthop: simplify code in nh_valid_get_bucket_req
Date: Sat, 17 Sep 2022 08:45:31 -0600 [thread overview]
Message-ID: <a297b958-b066-67bc-79ff-1b7d91553dbe@kernel.org> (raw)
In-Reply-To: <20220917063031.2172-1-williamsukatube@163.com>
On 9/17/22 12:30 AM, williamsukatube@163.com wrote:
> From: William Dean <williamsukatube@163.com>
>
> It could directly return 'nh_valid_get_bucket_req_res_bucket' to simplify code.
>
> Signed-off-by: William Dean <williamsukatube@163.com>
> ---
> net/ipv4/nexthop.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2022-09-17 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 6:30 williamsukatube
2022-09-17 14:45 ` David Ahern [this message]
2022-09-17 16:07 ` Christophe JAILLET
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=a297b958-b066-67bc-79ff-1b7d91553dbe@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=williamsukatube@163.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
all inboxes | Powered by JetHome®