[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200514.125751.2175402701800030395.davem@davemloft.net>
Date: Thu, 14 May 2020 12:57:51 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: David.Laight@...LAB.COM
Cc: joe@...ches.com, hch@....de, kuba@...nel.org, edumazet@...gle.com,
kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org, vyasevich@...il.com,
nhorman@...driver.com, marcelo.leitner@...il.com,
jmaloy@...hat.com, ying.xue@...driver.com,
drbd-dev@...ts.linbit.com, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-nvme@...ts.infradead.org, target-devel@...r.kernel.org,
linux-afs@...ts.infradead.org, linux-cifs@...r.kernel.org,
cluster-devel@...hat.com, ocfs2-devel@....oracle.com,
netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
ceph-devel@...r.kernel.org, rds-devel@....oracle.com,
linux-nfs@...r.kernel.org
Subject: Re: remove kernel_setsockopt and kernel_getsockopt
From: David Laight <David.Laight@...LAB.COM>
Date: Thu, 14 May 2020 08:29:30 +0000
> You need to export functions that do most of the socket options
> for all protocols.
If all in-tree users of this stuff are converted, there is no argument
for keeping these routines.
You seemed to be concerned about out of tree stuff. If so, that's not
of our concern.
Powered by blists - more mailing lists