From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: Anson Jacob <ansonjacob.aj@gmail.com>,
Staging List <devel@driverdev.osuosl.org>,
arve@android.com, riandrews@android.com,
Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: android: lowmemorykiller.c: Fix checkpatch warning
Date: Thu, 1 Sep 2016 17:36:21 +0200 [thread overview]
Message-ID: <20160901153621.GA24685@kroah.com> (raw)
In-Reply-To: <20160825152647.ts6oq4sanxlbuneh@acer>
On Thu, Aug 25, 2016 at 06:26:48PM +0300, Andrey Utkin wrote:
> On Thu, Aug 25, 2016 at 11:10:25AM -0400, Anson Jacob wrote:
> > Fix checkpatch.pl 'line over 80 characters' warning
> >
> > Signed-off-by: Anson Jacob <ansonjacob.aj@gmail.com>
> > ---
> > drivers/staging/android/lowmemorykiller.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c
> > index 45a1b4e..80d7adf 100644
> > --- a/drivers/staging/android/lowmemorykiller.c
> > +++ b/drivers/staging/android/lowmemorykiller.c
> > @@ -92,8 +92,8 @@ static unsigned long lowmem_scan(struct shrinker *s, struct shrink_control *sc)
> > int array_size = ARRAY_SIZE(lowmem_adj);
> > int other_free = global_page_state(NR_FREE_PAGES) - totalreserve_pages;
> > int other_file = global_node_page_state(NR_FILE_PAGES) -
> > - global_node_page_state(NR_SHMEM) -
> > - total_swapcache_pages();
> > + global_node_page_state(NR_SHMEM) -
> > + total_swapcache_pages();
> >
> > if (lowmem_adj_size < array_size)
> > array_size = lowmem_adj_size;
>
> Indeed original alignment on opening brace here doesn't make sense.
> I don't mind if your patch gets accepted, but out of curiosity I have opened
> this file in vim with kernel coding style plugin loaded
> (https://github.com/vivien/vim-linux-coding-style), selected the affected
> lines, and reindented the selection by pressing 'gq'. It ended up with this,
> being both shorter and simpler:
>
> diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c
> index 45a1b4e..3aef467 100644
> --- a/drivers/staging/android/lowmemorykiller.c
> +++ b/drivers/staging/android/lowmemorykiller.c
> @@ -92,8 +92,7 @@ static unsigned long lowmem_scan(struct shrinker *s, struct shrink_control *sc)
> int array_size = ARRAY_SIZE(lowmem_adj);
> int other_free = global_page_state(NR_FREE_PAGES) - totalreserve_pages;
> int other_file = global_node_page_state(NR_FILE_PAGES) -
> - global_node_page_state(NR_SHMEM) -
> - total_swapcache_pages();
> + global_node_page_state(NR_SHMEM) - total_swapcache_pages();
The original patch here is nicer to read, don't you think?
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-01 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 15:10 [PATCH] staging: android: lowmemorykiller.c: Fix checkpatch warning Anson Jacob
2016-08-25 15:26 ` Andrey Utkin
2016-09-01 15:36 ` Greg Kroah-Hartman [this message]
2016-09-01 18:19 ` Joe Perches
2016-09-01 18:33 ` Greg Kroah-Hartman
2016-09-01 18:42 ` Joe Perches
2016-09-01 21:19 ` Arve Hjønnevåg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160901153621.GA24685@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrey_utkin@fastmail.com \
--cc=ansonjacob.aj@gmail.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox