[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250530024527.3206724-1-kuni1840@gmail.com>
Date: Thu, 29 May 2025 19:45:26 -0700
From: Kuniyuki Iwashima <kuni1840@...il.com>
To: hch@....de
Cc: axboe@...nel.dk,
chuck.lever@...cle.com,
davem@...emloft.net,
edumazet@...gle.com,
horms@...nel.org,
jaka@...ux.ibm.com,
jlayton@...nel.org,
kbusch@...nel.org,
kuba@...nel.org,
kuni1840@...il.com,
kuniyu@...zon.com,
linux-nfs@...r.kernel.org,
linux-nvme@...ts.infradead.org,
linux-rdma@...r.kernel.org,
matttbe@...nel.org,
mptcp@...ts.linux.dev,
netdev@...r.kernel.org,
pabeni@...hat.com,
sfrench@...ba.org,
wenjia@...ux.ibm.com,
willemb@...gle.com
Subject: Re: [PATCH v2 net-next 2/7] socket: Rename sock_create_kern() to __sock_create_kern().
From: Christoph Hellwig <hch@....de>
Date: Mon, 26 May 2025 07:30:13 +0200
> On Fri, May 23, 2025 at 11:21:08AM -0700, Kuniyuki Iwashima wrote:
> > Let's rename sock_create_kern() to __sock_create_kern() as a special
> > API and add a fat documentation.
> >
> > The next patch will add sock_create_kern() that holds netns refcnt.
>
> Maybe do this before patch 1 to reduce the churn of just touching a
> lot of the same callers again?
Makes sense, will do.
Powered by blists - more mailing lists