From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, xudong.hao@intel.com
Subject: Re: [linux-next:master] [vmscan] a7694ff11a: kernel-selftests.kvm.access_tracking_perf_test.fail
Date: Wed, 16 Jul 2025 11:22:47 +0100 [thread overview]
Message-ID: <20250716102247.GB2580412@ZenIV> (raw)
In-Reply-To: <202507160818.49e37313-lkp@intel.com>
On Wed, Jul 16, 2025 at 03:54:05PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "kernel-selftests.kvm.access_tracking_perf_test.fail" on:
>
> commit: a7694ff11aa9d97d0f690351a964544849e5158d ("vmscan: don't bother with debugfs_real_fops()")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 0be23810e32e6d0a17df7c0ebad895ba2c210fc4]
Argh... See https://lore.kernel.org/all/20250704040720.GP1880847@ZenIV/
Sorry, hadn't checked if the updated variant got picked ;-/
prev parent reply other threads:[~2025-07-16 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 7:54 kernel test robot
2025-07-16 10:22 ` Al Viro [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=20250716102247.GB2580412@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=willy@infradead.org \
--cc=xudong.hao@intel.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