From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master] BUILD REGRESSION e6ada6df471f847da3b09b357e246c62335bc0bb
Date: Wed, 2 Mar 2022 15:30:32 -0800 [thread overview]
Message-ID: <20220302153032.50d974536285a6aa518b03f5@linux-foundation.org> (raw)
In-Reply-To: <621ef3ff.CVMqqqmxwvCkBine%lkp@intel.com>
There are many warnings here in arch/*, drivers/gpu, net, scsi, etc.
The people who own that code surely won't be seeing these emails.
Can I suggest you spread them around a bit more? A cc to the relevant
subsystem's mailing list would suffice - probably it isn't necessary to
cc individuals directly.
next prev parent reply other threads:[~2022-03-02 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 4:35 kernel test robot
2022-03-02 23:30 ` Andrew Morton [this message]
2022-03-03 0:17 ` Philip Li
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=20220302153032.50d974536285a6aa518b03f5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@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