From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>, Linux MM <linux-mm@kvack.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
linux-mediatek@lists.infradead.org,
linux-riscv@lists.infradead.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 5/9] m68k/mm: use __ClearPageReserved()
Date: Mon, 14 Jan 2019 15:02:50 +0100 [thread overview]
Message-ID: <CAMuHMdWEChb4+tf0m_qN9Mc6Am5T0rZLqAn6QsQ8NdMOCRPySQ@mail.gmail.com> (raw)
In-Reply-To: <20190114125903.24845-6-david@redhat.com>
On Mon, Jan 14, 2019 at 1:59 PM David Hildenbrand <david@redhat.com> wrote:
> The PG_reserved flag is cleared from memory that is part of the kernel
> image (and therefore marked as PG_reserved). Avoid using PG_reserved
> directly.
>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: David Hildenbrand <david@redhat.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
BTW, it's a pity ctags doesn't know where __ClearPageReserved()
is defined.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-01-14 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 12:58 [PATCH v2 0/9] mm: PG_reserved cleanups and documentation David Hildenbrand
2019-01-14 12:58 ` [PATCH v2 1/9] agp: efficeon: no need to set PG_reserved on GATT tables David Hildenbrand
2019-01-14 12:58 ` [PATCH v2 2/9] s390/vdso: don't clear PG_reserved David Hildenbrand
2019-01-14 12:58 ` [PATCH v2 3/9] powerpc/vdso: " David Hildenbrand
2019-01-14 12:58 ` [PATCH v2 4/9] riscv/vdso: " David Hildenbrand
2019-01-15 15:36 ` Christoph Hellwig
2019-01-14 12:58 ` [PATCH v2 5/9] m68k/mm: use __ClearPageReserved() David Hildenbrand
2019-01-14 14:02 ` Geert Uytterhoeven [this message]
2019-01-14 12:59 ` [PATCH v2 6/9] arm64: kexec: no need to ClearPageReserved() David Hildenbrand
2019-01-14 15:50 ` Bhupesh Sharma
2019-01-25 16:25 ` Catalin Marinas
2019-01-14 12:59 ` [PATCH v2 7/9] arm64: kdump: No need to mark crashkernel pages manually PG_reserved David Hildenbrand
2019-01-14 15:52 ` Bhupesh Sharma
2019-01-25 16:28 ` Catalin Marinas
2019-01-14 12:59 ` [PATCH v2 8/9] ia64: perfmon: Don't mark buffer pages as PG_reserved David Hildenbrand
2019-01-14 12:59 ` [PATCH v2 9/9] mm: better document PG_reserved David Hildenbrand
2019-01-15 15:38 ` [PATCH v2 0/9] mm: PG_reserved cleanups and documentation Christoph Hellwig
2019-01-15 15:53 ` David Hildenbrand
2019-01-21 11:36 ` David Hildenbrand
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=CAMuHMdWEChb4+tf0m_qN9Mc6Am5T0rZLqAn6QsQ8NdMOCRPySQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.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).