[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgpnR9sBeie_z0xA3mYzG50Oiw1jZjyHt0eLX6p45ARvQ@mail.gmail.com>
Date: Thu, 28 May 2020 11:43:13 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Christoph Hellwig <hch@....de>
Cc: Al Viro <viro@...iv.linux.org.uk>, Ian Kent <raven@...maw.net>,
David Howells <dhowells@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
NetFilter <netfilter-devel@...r.kernel.org>
Subject: Re: [PATCH 09/14] fs: don't change the address limit for ->write_iter
in __kernel_write
On Wed, May 27, 2020 at 10:41 PM Christoph Hellwig <hch@....de> wrote:
>
> -ssize_t __kernel_write(struct file *file, const void *buf, size_t count, loff_t *pos)
> +ssize_t __kernel_write(struct file *file, const void *buf, size_t count,
> + loff_t *pos)
Please don't do these kinds of pointless whitespace changes.
If you have an actual 80x25 vt100 sitting in a corner, it's not really
conducive to kernel development any more.
Yes, yes, we'd like to have shorter lines for new code, but no, don't
do silly line breaks that just makes old code look and grep worse.
Linus
Powered by blists - more mailing lists