Thread (15 messages) 15 messages, 6 authors, 2019-05-24

Re: [PATCH v1 1/2] open: add close_range()

From: Christian Brauner <christian@brauner.io>
Date: 2019-05-24 09:57:17
Also in: linux-alpha, linux-api, linux-arch, linux-arm-kernel, linux-fsdevel, linux-kselftest, linux-mips, linux-sh, lkml, sparclinux

On Fri, May 24, 2019 at 09:43:53AM +0200, Arnd Bergmann wrote:
On Thu, May 23, 2019 at 6:33 PM Christian Brauner [off-list ref] wrote:
quoted
On Thu, May 23, 2019 at 07:22:17PM +0300, Konstantin Khlebnikov wrote:
quoted
On 22.05.2019 18:52, Christian Brauner wrote:> This adds the close_range() syscall. It allows to efficiently close a range
quoted
  22 files changed, 100 insertions(+), 9 deletions(-)
It would be better to split arch/ wiring into separate patch for better readability.
Ok. You mean only do x86 - seems to be the standard - and then move the
others into a separate patch? Doesn't seem worth to have a patch
per-arch, I'd think.
I think I would prefer the first patch to just add the call without wiring it up
anywhere, and a second patch do add it on all architectures including x86.
I've split this into two patches and also bumped arm64
__NR_compat_syscalls that I've missed before as you mentioned!

Thanks!
Christian
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help