linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: CGEL <cgel.zte@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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, 13 May 2022 01:30:25 +0000	[thread overview]
Message-ID: <627db4b2.1c69fb81.6d1eb.1e81@mx.google.com> (raw)
In-Reply-To: <20220505215706.dd5f27399d99ef53cfb9244c@linux-foundation.org>

On Thu, May 05, 2022 at 09:57:06PM -0700, Andrew Morton wrote:
> On Fri, 6 May 2022 02:48:04 +0000 CGEL <cgel.zte@gmail.com> wrote:
> 
> >     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's still in my tree, part of a small queue of post-linux-next patches
> which I'm not presently distributing.  I'll bring it back soon.

Thanks! I want to write some other patches base on this patch, so please
notify me when it back.


      reply	other threads:[~2022-05-13  1:30 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
2022-05-06  4:57     ` Andrew Morton
2022-05-13  1:30       ` CGEL [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=627db4b2.1c69fb81.6d1eb.1e81@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).