linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: zhouzihan30 <15645113830zzh@gmail.com>
To: liam.howlett@oracle.com
Cc: 15645113830zzh@gmail.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	yaowenchao@jd.com, zhouzihan30@jd.com
Subject: Re: [PATCH V1] mm: fix bug in some memory information update
Date: Tue, 17 Dec 2024 16:30:27 +0800	[thread overview]
Message-ID: <20241217083026.29122-1-zhouzihan30@jd.com> (raw)
In-Reply-To: <edigemkxkze3iicku3orrufdadevca33ndqxw2etqvustykpv6@smaext2j3bzp>

Thank you for your reply. The title of this patch is indeed not good.
We are planning to rename it as "mm: page_alloc: fix missed updates of 
lowmem_reserve in adjust_managed_page_count". Is it OK?

< The subject of this patch is really poor.  "some memory information"?
< 
< considering the text below is so much more descriptive, could we have a
< meaningful subject?  You will not get the proper people looking at this
< without a decent subject.  At least make it "mm/page_alloc" ?

Regarding Signed-off-by, we are sorry that we do not have a particular
 good way. When we are on the intranet, we use jd.com email. However,
this email cannot send emails externally, so we used our own Gmail as the
 sending email. My name is Zihan Zhou, and zhouzihan30 is my internal ERP.
 I also rely on this account to submit information on the intranet. 
Do we have to prepare a new account for kernel submission?

< Who are these people, really?
< 
< https://www.kernel.org/doc/html/v6.12/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
< 
< Also, the Signed-off-by doesn't match the sending email (gmail vs
< jd.com)?


      reply	other threads:[~2024-12-17  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  8:16 zhouzihan30
2024-12-13 15:44 ` Liam R. Howlett
2024-12-17  8:30   ` zhouzihan30 [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=20241217083026.29122-1-zhouzihan30@jd.com \
    --to=15645113830zzh@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yaowenchao@jd.com \
    --cc=zhouzihan30@jd.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