Re: [PATCH] delayacct: track delays from write-protect copy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: CGEL <cgel.zte@xxxxxxxxx>
Subject: Re: [PATCH] delayacct: track delays from write-protect copy
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 5 May 2022 21:57:06 -0700
Cc: david@xxxxxxxxxx, kbuild-all@xxxxxxxxxxxx, corbet@xxxxxxx, bsingharora@xxxxxxxxx, mike.kravetz@xxxxxxxxxx, yang.yang29@xxxxxxxxxx, sfr@xxxxxxxxxxxxxxxx, thomas.orgis@xxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <62748c65.1c69fb81.2aa2d.4a7b@mx.google.com>
References: <20220408103708.2495882-1-yang.yang29@zte.com.cn> <202204082220.1w5xTsNt-lkp@intel.com> <62748c65.1c69fb81.2aa2d.4a7b@mx.google.com>

On Fri, 6 May 2022 02:48:04 +0000 CGEL <cgel.zte@xxxxxxxxx> 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.

Follow-Ups:
- Re: [PATCH] delayacct: track delays from write-protect copy
  - From: CGEL

References:
- [PATCH] delayacct: track delays from write-protect copy
  - From: cgel . zte
- Re: [PATCH] delayacct: track delays from write-protect copy
  - From: kernel test robot
- Re: [PATCH] delayacct: track delays from write-protect copy
  - From: CGEL

Prev by Date: Re: [PATCH v23 3/6] arm64: kdump: Reimplement crashkernel=X
Next by Date: [PATCH v2 0/1] Allow setting hostname before userspace starts
Previous by thread: Re: [PATCH] delayacct: track delays from write-protect copy
Next by thread: Re: [PATCH] delayacct: track delays from write-protect copy
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]