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,
SeongJae Park <sj@kernel.org>
Subject: Re: mmotm 2021-12-29-20-07 uploaded (mm/damon)
Date: Wed, 29 Dec 2021 22:27:00 -0800 [thread overview]
Message-ID: <a57f9bc4-2c1b-f819-17a6-2e1d2f9dd173@infradead.org> (raw)
In-Reply-To: <20211230040740.SbquJAFf5%akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
Hi--
On 12/29/21 20:07, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2021-12-29-20-07 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.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
On i386:
../mm/damon/vaddr.c: In function ‘damon_hugetlb_mkold’:
../mm/damon/vaddr.c:402:17: warning: unused variable ‘h’ [-Wunused-variable]
struct hstate *h = hstate_vma(vma);
^
../mm/shmem.c:3992:5: error: conflicting types for ‘shmem_unuse’
int shmem_unuse(unsigned int type, unsigned long *fs_pages_to_unuse)
^~~~~~~~~~~
In file included from ../include/linux/khugepaged.h:6:0,
from ../mm/shmem.c:37:
../include/linux/shmem_fs.h:86:5: note: previous declaration of ‘shmem_unuse’ was here
int shmem_unuse(unsigned int type);
^~~~~~~~~~~
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r1958.gz --]
[-- Type: application/gzip, Size: 29652 bytes --]
next prev parent reply other threads:[~2021-12-30 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 4:07 mmotm 2021-12-29-20-07 uploaded akpm
2021-12-30 6:27 ` Randy Dunlap [this message]
2021-12-30 6:33 ` mmotm 2021-12-29-20-07 uploaded (mm/damon) Baolin Wang
2021-12-30 17:32 ` Randy Dunlap
2021-12-30 8:42 ` mmotm 2021-12-29-20-07 uploaded SeongJae Park
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=a57f9bc4-2c1b-f819-17a6-2e1d2f9dd173@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=sfr@canb.auug.org.au \
--cc=sj@kernel.org \
/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).