From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Pavel Tatashin <pasha.tatashin@soleen.com>
Subject: Re: mmotm 2021-02-02-20-19 uploaded (mm/...)
Date: Tue, 2 Feb 2021 23:32:46 -0800 [thread overview]
Message-ID: <8bf42bd2-1175-f26b-20b2-99b8c4a56aef@infradead.org> (raw)
In-Reply-To: <20210203042026.kpYSeiK1r%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On 2/2/21 8:20 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-02-02-20-19 has been uploaded to
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> https://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
Please use the attached config file for x86_64.
It had over 6000 errors (using make -ik).
Dumb script build summary for one config:
> buildsummary.pl build-r7599.out
file: arch/x86/boot/header.S: errors: 1, warnings: 0
file: fs/xfs/xfs_log.c: errors: 0, warnings: 1
file: include/asm-generic/memory_model.h: errors: 3070, warnings: 2
file: include/linux/mm.h: errors: 3072, warnings: 0
file: ld: errors: 0, warnings: 1
build-r7599.out: totals: error/warning files: 5, errors: 6143, warnings: 4, Section mismatches: 0
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r7599.gz --]
[-- Type: application/gzip, Size: 41224 bytes --]
prev parent reply other threads:[~2021-02-03 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 4:20 mmotm 2021-02-02-20-19 uploaded akpm
2021-02-03 7:32 ` Randy Dunlap [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=8bf42bd2-1175-f26b-20b2-99b8c4a56aef@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=sfr@canb.auug.org.au \
/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