From: CGEL <cgel.zte@gmail.com>
To: akpm@linux-foundation.org
Cc: akpm@linux-foundation.org, david@redhat.com,
kbuild-all@lists.01.org, corbet@lwn.net, bsingharora@gmail.com,
mike.kravetz@oracle.com, yang.yang29@zte.com.cn,
sfr@canb.auug.org.au, thomas.orgis@uni-hamburg.de,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] delayacct: track delays from write-protect copy
Date: Fri, 6 May 2022 02:48:04 +0000 [thread overview]
Message-ID: <62748c65.1c69fb81.2aa2d.4a7b@mx.google.com> (raw)
In-Reply-To: <202204082220.1w5xTsNt-lkp@intel.com>
Hi
I found this patch is first merged into linux-next, and dropped silently
without sending any mail. Could you please tell the reason? Thanks!
It was merged by this:
https://lore.kernel.org/all/20220409031312.583D3C385A4@smtp.kernel.org/
next prev parent reply other threads:[~2022-05-06 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:37 [PATCH] delayacct: track delays from write-protect copy cgel.zte
2022-04-08 15:02 ` kernel test robot
2022-05-06 2:48 ` CGEL [this message]
2022-05-06 4:57 ` Andrew Morton
2022-05-13 1:30 ` CGEL
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=62748c65.1c69fb81.2aa2d.4a7b@mx.google.com \
--to=cgel.zte@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.orgis@uni-hamburg.de \
--cc=yang.yang29@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).