From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: mmotm 2020-01-21-13-28 uploaded (struct proc_ops)
Date: Tue, 21 Jan 2020 19:19:22 -0800 [thread overview]
Message-ID: <d18345b6-616f-4ea3-7b9e-956f8edc26b7@infradead.org> (raw)
In-Reply-To: <20200121212915.APuBK%akpm@linux-foundation.org>
On 1/21/20 1:29 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2020-01-21-13-28 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
and when CONFIG_PROC_FS is not set/enabled, kernel/sched/psi.c gets:
../kernel/sched/psi.c: In function ‘psi_proc_init’:
../kernel/sched/psi.c:1287:56: error: macro "proc_create" requires 4 arguments, but only 3 given
proc_create("pressure/cpu", 0, NULL &psi_cpu_proc_ops);
^
../kernel/sched/psi.c:1287:3: error: ‘proc_create’ undeclared (first use in this function); did you mean ‘sock_create’?
proc_create("pressure/cpu", 0, NULL &psi_cpu_proc_ops);
^~~~~~~~~~~
sock_create
--
~Randy
next prev parent reply other threads:[~2020-01-22 3:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 21:29 mmotm 2020-01-21-13-28 uploaded akpm
2020-01-22 2:25 ` mmotm 2020-01-21-13-28 uploaded (convert everything to struct proc_ops) Randy Dunlap
2020-01-22 3:19 ` Randy Dunlap [this message]
2020-01-26 15:07 ` mmotm 2020-01-21-13-28 uploaded (struct proc_ops) Alexey Dobriyan
2020-01-22 3:54 ` mmotm 2020-01-21-13-28 uploaded (drivers/gpu/drm/i915/gt/intel_lrc.c) Randy Dunlap
2020-01-22 4:47 ` mmotm 2020-01-21-13-28 uploaded (nouveau) Randy Dunlap
2020-01-22 4:56 ` mmotm 2020-01-21-13-28 uploaded (smack) Randy Dunlap
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=d18345b6-616f-4ea3-7b9e-956f8edc26b7@infradead.org \
--to=rdunlap@infradead.org \
--cc=adobriyan@gmail.com \
--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 \
/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).