public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: gaoxu <gaoxu2@honor.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: 回复: 回复: linux-next: Signed-off-by missing for commit in the mm tree
Date: Tue, 20 Aug 2024 03:41:45 +0000	[thread overview]
Message-ID: <e85bad8d463e4f529cabfc24292f47aa@honor.com> (raw)
In-Reply-To: <5cc94991f4a14d56a6c9a19ec42a94cd@honor.com>

> >
> > On Mon, 19 Aug 2024 03:56:04 +0000 gaoxu <gaoxu2@honor.com> wrote:
> >
> > > >
> > > > Hi all,
> > > >
> > > > Commit
> > > >
> > > >   ccbb07b2a3a7 ("mm: add lazyfree folio to lru tail")
> > > >
> > > > is missing a Signed-off-by from its author.
> > > >
> > > > Actually the Author is "gaoxu <gaoxu2@honor.com>" while the
> > > > Signed-off-by is "gao xu <gaoxu2@hihonor.com>".
> > > I apologize for the mistake. Are there any remedial measures?
> > > I will be more careful next time.
> >
> > Well, which address should we use?
> Use gaoxu <gaoxu2@honor.com>
Our company has recently launched a new domain name:honor.com, while the original domain name:hihonor.com will also continue to be maintained.
Therefore, the IT department recommends using gaoxu2@honor.com.  However, if continue to use gaoxu2@hihonor.com, it will also work for communication.
So, recommends use gaoxu <gaoxu2@honor.com>,  However using gao xu <gaoxu2@hihonor.com> is also fine.

      reply	other threads:[~2024-08-20  3:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 22:03 linux-next: Signed-off-by missing for commit in the mm tree Stephen Rothwell
2024-08-19  3:56 ` 回复: " gaoxu
2024-08-20  0:33   ` Andrew Morton
2024-08-20  1:26     ` 回复: " gaoxu
2024-08-20  3:41       ` gaoxu [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=e85bad8d463e4f529cabfc24292f47aa@honor.com \
    --to=gaoxu2@honor.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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