[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200528.111205.608949763790224771.davem@davemloft.net>
Date: Thu, 28 May 2020 11:12:05 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: hch@....de
Cc: kuba@...nel.org, edumazet@...gle.com, kuznet@....inr.ac.ru,
yoshfuji@...ux-ipv6.org, jmaloy@...hat.com, ying.xue@...driver.com,
drbd-dev@...ts.linbit.com, 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,
ceph-devel@...r.kernel.org, rds-devel@....oracle.com,
linux-nfs@...r.kernel.org, tipc-discussion@...ts.sourceforge.net
Subject: Re: remove most callers of kernel_setsockopt v3
From: Christoph Hellwig <hch@....de>
Date: Thu, 28 May 2020 07:12:08 +0200
> this series removes most callers of the kernel_setsockopt functions, and
> instead switches their users to small functions that implement setting a
> sockopt directly using a normal kernel function call with type safety and
> all the other benefits of not having a function call.
>
> In some cases these functions seem pretty heavy handed as they do
> a lock_sock even for just setting a single variable, but this mirrors
> the real setsockopt implementation unlike a few drivers that just set
> set the fields directly.
...
Series applied, thanks Christoph.
Powered by blists - more mailing lists