linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pintu Agarwal <pintu.ping@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: winterver <295107659@qq.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org,
	Pintu Kumar <quic_pintu@quicinc.com>
Subject: Re: [PATCH] mm: Remove 'return;' at the end of void cma_activate_area()
Date: Wed, 20 Nov 2024 10:09:55 +0530	[thread overview]
Message-ID: <CAOuPNLi0f-Bo5mzuKn2CPXNy70jtbsOuonV9cdmKZB8jKu9jOA@mail.gmail.com> (raw)
In-Reply-To: <20241119191344.53712-1-sj@kernel.org>

On Wed, 20 Nov 2024 at 00:43, SeongJae Park <sj@kernel.org> wrote:
>
> Hello,
>
> On Tue, 19 Nov 2024 19:59:40 +0800 winterver <295107659@qq.com> wrote:
>
> > From: Jiale Yang <295107659@qq.com>
> >
> > Remove 'return;' at the end of void cma_activate_area(). It's a void
> > function, so an ending return statement is unnecessary.
> >
> > Signed-off-by: Jiale Yang <295107659@qq.com>
> > ---
> >  mm/cma.c | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 2d9fae939..070399bce 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -135,7 +135,6 @@ static void __init cma_activate_area(struct cma *cma)
> >       totalcma_pages -= cma->count;
> >       cma->count = 0;
> >       pr_err("CMA area %s could not be activated\n", cma->name);
> > -     return;
> >  }
>
> Looks good to me.  But, seems a same change[1] from Pintu Kumar has already
> merged into mm-unstable?
>
> [1] https://lore.kernel.org/20240927181637.19941-1-quic_pintu@quicinc.com
>
Yes, this [1] is already part of linux-next now.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20241118&id=1fa00a568d113db279f683f40636cf72cf73a55d


      reply	other threads:[~2024-11-20  4:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 11:59 winterver
2024-11-19 12:59 ` David Hildenbrand
2024-11-19 19:13 ` SeongJae Park
2024-11-20  4:39   ` Pintu Agarwal [this message]

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=CAOuPNLi0f-Bo5mzuKn2CPXNy70jtbsOuonV9cdmKZB8jKu9jOA@mail.gmail.com \
    --to=pintu.ping@gmail.com \
    --cc=295107659@qq.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=quic_pintu@quicinc.com \
    --cc=sj@kernel.org \
    /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