From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Jan Karcher <jaka@linux.ibm.com>,
Wen Gu <guwen@linux.alibaba.com>,
Tony Lu <tonylu@linux.alibaba.com>,
"D . Wythe" <alibuda@linux.alibaba.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>,
<mptcp@lists.linux.dev>, <linux-s390@vger.kernel.org>,
Gerd Bayer <gbayer@linux.ibm.com>
Subject: Re: [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.
Date: Thu, 15 Feb 2024 07:07:02 -0800 [thread overview]
Message-ID: <20240215070702.717e8e9b@kernel.org> (raw)
In-Reply-To: <20240214195407.3175-1-kuniyu@amazon.com>
On Wed, 14 Feb 2024 11:54:07 -0800 Kuniyuki Iwashima wrote:
> Recently, commit 8e5443d2b866 ("net: remove SOCK_DEBUG leftovers")
> removed the last users of SOCK_DEBUG(), and commit b1dffcf0da22 ("net:
> remove SOCK_DEBUG macro") removed the macro.
Unrelated to this patch but speaking of deprecating things - do you
want to go ahead with deleting DCCP? I don't recall our exact plan,
I thought it was supposed to happen early in the year :)
next prev parent reply other threads:[~2024-02-15 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 19:54 [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Kuniyuki Iwashima
2024-02-14 20:50 ` net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results MPTCP CI
2024-02-14 21:04 ` MPTCP CI
2024-02-15 9:58 ` [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Matthieu Baerts
2024-02-15 19:37 ` Kuniyuki Iwashima
2024-02-15 10:58 ` net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results MPTCP CI
2024-02-15 11:13 ` MPTCP CI
2024-02-15 14:14 ` [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Alexandra Winter
2024-02-15 19:39 ` Kuniyuki Iwashima
2024-02-15 15:07 ` Jakub Kicinski [this message]
2024-02-15 16:05 ` Paolo Abeni
2024-02-15 16:10 ` 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=20240215070702.717e8e9b@kernel.org \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gbayer@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-s390@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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 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.