From: yajun.deng@linux.dev
To: "Matthieu Baerts" <matthieu.baerts@tessares.net>,
davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: Remove redundant if statements
Date: Fri, 06 Aug 2021 09:13:21 +0000 [thread overview]
Message-ID: <a9ed105aa609b619492044da3e22ff65@linux.dev> (raw)
In-Reply-To: <4b175501-50c1-fedf-1eaf-05c0de67c3c8@tessares.net>
August 6, 2021 4:58 PM, "Matthieu Baerts" <matthieu.baerts@tessares.net> wrote:
> Hi Yajun,
>
> Thank you for sharing this patch.
>
> On 06/08/2021 08:38, Yajun Deng wrote:
>
>> The if statement already move into sock_{put , hold},
>> just remove it.
>
> I was wondering in which subtree you had 'sock_put' checking the socket
> pointer but then I realised you sent another patch just before adding
> this check: "net: sock: add the case if sk is NULL"
>
> Please next time send them in the same series to clearly indicate that
> this is the 2nd patch (2/2) and it depends on patch 1/2.
>
OK, Thank you for your advice.
> Related to the modification in MPTCP part: it looks OK but we do a few
> other calls to 'sock_put()' where we don't need to check if the socket
> is NULL or not.
>
> In other words, if your patch "net: sock: add the case if sk is NULL" is
> accepted, then the modification in "net/mptcp/subflow.c" is OK for us.
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next prev parent reply other threads:[~2021-08-06 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 6:38 [PATCH net-next] net: Remove redundant if statements Yajun Deng
2021-08-06 8:58 ` Matthieu Baerts
2021-08-06 9:13 ` yajun.deng [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-05 11:55 Yajun Deng
2021-08-05 12:30 ` patchwork-bot+netdevbpf
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=a9ed105aa609b619492044da3e22ff65@linux.dev \
--to=yajun.deng@linux.dev \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthieu.baerts@tessares.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.