From: David Miller <davem@davemloft.net>
To: liuzhiqiang26@huawei.com
Cc: edumazet@google.com, netdev@vger.kernel.org,
mingfangsen@huawei.com, zhoukang7@huawei.com,
wangxiaogang3@huawei.com
Subject: Re: [PATCH net] inet_connection_sock: remove unused parameter of reqsk_queue_unlink func
Date: Wed, 05 Jun 2019 19:19:03 -0700 (PDT) [thread overview]
Message-ID: <20190605.191903.756231080836216664.davem@davemloft.net> (raw)
In-Reply-To: <3792c359-98b3-c312-d87a-204a846a3c11@huawei.com>
From: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Date: Thu, 6 Jun 2019 10:06:55 +0800
>> From: Zhiqiang Liu <liuzhiqiang26@huawei.com>
>> Date: Wed, 5 Jun 2019 18:49:49 +0800
>>
>>> small cleanup: "struct request_sock_queue *queue" parameter of reqsk_queue_unlink
>>> func is never used in the func, so we can remove it.
>>>
>>> Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
>>
>> Applied, thanks.
>>
>
> Hi, David Miller.
> So sorry for forgetting to sign partner's name who find the cleanup together.
> I have sent v2 patch with my partner's signature.
>
> I am so sorry for the mistake.
It is already pushed out to my public GIT tree and the commit is immutable.
next prev parent reply other threads:[~2019-06-06 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 14:55 [PATCH net] tcp: avoid creating multiple req socks with the same tuples Mao Wenan
2019-06-04 15:24 ` Eric Dumazet
2019-06-05 2:06 ` maowenan
2019-06-05 3:16 ` Eric Dumazet
2019-06-05 8:52 ` Zhiqiang Liu
2019-06-05 10:49 ` [PATCH net] inet_connection_sock: remove unused parameter of reqsk_queue_unlink func Zhiqiang Liu
2019-06-05 14:10 ` Eric Dumazet
2019-06-06 1:49 ` David Miller
2019-06-06 2:06 ` Zhiqiang Liu
2019-06-06 2:19 ` David Miller [this message]
2019-06-06 2:29 ` Zhiqiang Liu
2019-06-05 14:18 ` [PATCH net] tcp: avoid creating multiple req socks with the same tuples Eric Dumazet
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=20190605.191903.756231080836216664.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=liuzhiqiang26@huawei.com \
--cc=mingfangsen@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=wangxiaogang3@huawei.com \
--cc=zhoukang7@huawei.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).