From: Jakub Kicinski <kuba@kernel.org>
To: yajun.deng@linux.dev
Cc: "kernel test robot" <lkp@intel.com>,
davem@davemloft.net, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net, trond.myklebust@hammerspace.com,
anna.schumaker@netapp.com, kbuild-all@lists.01.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, mptcp@lists.linux.dev,
Denis Kirjanov <kda@linux-powerpc.org>
Subject: Re: [PATCH net-next] net: Modify sock_set_keepalive() for more scenarios
Date: Tue, 3 Aug 2021 08:59:30 -0700 [thread overview]
Message-ID: <20210803085930.103d37dc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <a37faefd6dcad9f01212d60f8bb32f4f@linux.dev>
On Tue, 03 Aug 2021 11:42:39 +0000 yajun.deng@linux.dev wrote:
> The tcp_create_listen_sock() function was already dropped in commit
> <2dc6b1158c28c3a5e86d162628810312f98d5e97> by Alexander Aring.
We don't have the commit you're quoting in the networking trees.
You should modify tcp_create_listen_sock() and we'll deal with
the conflict during the merge window.
Unless obviously you should wait and "send the patch within a context
of other scenarios".. (I'm unclear on what Denis is referring to.)
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH net-next] net: Modify sock_set_keepalive() for more scenarios
Date: Tue, 03 Aug 2021 08:59:30 -0700 [thread overview]
Message-ID: <20210803085930.103d37dc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <a37faefd6dcad9f01212d60f8bb32f4f@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On Tue, 03 Aug 2021 11:42:39 +0000 yajun.deng(a)linux.dev wrote:
> The tcp_create_listen_sock() function was already dropped in commit
> <2dc6b1158c28c3a5e86d162628810312f98d5e97> by Alexander Aring.
We don't have the commit you're quoting in the networking trees.
You should modify tcp_create_listen_sock() and we'll deal with
the conflict during the merge window.
Unless obviously you should wait and "send the patch within a context
of other scenarios".. (I'm unclear on what Denis is referring to.)
next prev parent reply other threads:[~2021-08-03 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 8:25 [PATCH net-next] net: Modify sock_set_keepalive() for more scenarios Yajun Deng
2021-08-03 9:44 ` Denis Kirjanov
2021-08-03 9:44 ` Denis Kirjanov
2021-08-03 11:28 ` kernel test robot
2021-08-03 11:28 ` kernel test robot
2021-08-03 11:42 ` yajun.deng
2021-08-03 11:42 ` yajun.deng
2021-08-03 15:59 ` Jakub Kicinski [this message]
2021-08-03 15:59 ` Jakub Kicinski
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=20210803085930.103d37dc@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=anna.schumaker@netapp.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=yajun.deng@linux.dev \
/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.