[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190228102229.dec5e125fc65a3ff7c6f865f@linux-foundation.org>
Date: Thu, 28 Feb 2019 10:22:29 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: William Kucharski <william.kucharski@...cle.com>
Cc: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Johannes Weiner <hannes@...xchg.org>,
Vlastimil Babka <vbabka@...e.cz>,
Rik van Riel <riel@...riel.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...nel.org>,
Mel Gorman <mgorman@...hsingularity.net>
Subject: Re: [PATCH v2 2/4] mm: remove zone_lru_lock() function access
->lru_lock directly
On Thu, 28 Feb 2019 05:53:37 -0700 William Kucharski <william.kucharski@...cle.com> wrote:
> > On Feb 28, 2019, at 1:33 AM, Andrey Ryabinin <aryabinin@...tuozzo.com> wrote:
>
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index a9852ed7b97f..2d081a32c6a8 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -1614,8 +1614,8 @@ static __always_inline void update_lru_sizes(struct lruvec *lruvec,
> >
> > }
> >
> > -/*
> > - * zone_lru_lock is heavily contended. Some of the functions that
> > +/**
>
> Nit: Remove the extra asterisk here; the line should then revert to being unchanged from
> the original.
I don't think so. This kernedoc comment was missing its leading /**.
The patch fixes that.
Powered by blists - more mailing lists