[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200518062255.GB15641@infradead.org>
Date: Sun, 17 May 2020 23:22:55 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>, viro@...iv.linux.org.uk,
gregkh@...uxfoundation.org, rafael@...nel.org,
ebiederm@...ssion.com, jeyu@...nel.org, jmorris@...ei.org,
keescook@...omium.org, paul@...l-moore.com,
stephen.smalley.work@...il.com, eparis@...isplace.org,
nayna@...ux.ibm.com, zohar@...ux.ibm.com,
scott.branden@...adcom.com, dan.carpenter@...cle.com,
skhan@...uxfoundation.org, geert@...ux-m68k.org,
tglx@...utronix.de, bauerman@...ux.ibm.com, dhowells@...hat.com,
linux-integrity@...r.kernel.org, linux-fsdevel@...r.kernel.org,
kexec@...ts.infradead.org, linux-security-module@...r.kernel.org,
selinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] fs: reduce export usage of kerne_read*() calls
On Fri, May 15, 2020 at 09:29:33PM +0000, Luis Chamberlain wrote:
> On Wed, May 13, 2020 at 11:17:36AM -0700, Christoph Hellwig wrote:
> > Can you also move kernel_read_* out of fs.h? That header gets pulled
> > in just about everywhere and doesn't really need function not related
> > to the general fs interface.
>
> Sure, where should I dump these?
Maybe a new linux/kernel_read_file.h? Bonus points for a small top
of the file comment explaining the point of the interface, which I
still don't get :)
Powered by blists - more mailing lists