From: Christoph Hellwig <hch@lst.de>
To: x86@kernel.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: remove various unused set_memory_* related functions and exports v2
Date: Mon, 26 Aug 2019 09:55:53 +0200 [thread overview]
Message-ID: <20190826075558.8125-1-hch@lst.de> (raw)
Hi all,
while looking into implementing a DMA memory allocator for PCIe unsnooped
transactions I've started looking at the set_memory_* and related APIs,
and it turns out that many of them are unused. Fix for that below.
Changes since v2:
- dropped the already merged arm64 patch
- fix a subject line to not mention the wrong functions
next reply other threads:[~2019-08-26 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 7:55 Christoph Hellwig [this message]
2019-08-26 7:55 ` [PATCH 1/5] x86: unexport set_memory_x and set_memory_nx Christoph Hellwig
2019-09-03 8:31 ` [tip: x86/mm] x86/mm: Unexport set_memory_x() and set_memory_nx() tip-bot2 for Christoph Hellwig
2019-08-26 7:55 ` [PATCH 2/5] x86: remove the unused set_memory_array_* functions Christoph Hellwig
2019-09-03 8:31 ` [tip: x86/mm] x86/mm: Remove the unused set_memory_array_*() functions tip-bot2 for Christoph Hellwig
2019-08-26 7:55 ` [PATCH 3/5] x86: remove set_pages_x and set_pages_nx Christoph Hellwig
2019-09-03 8:31 ` [tip: x86/mm] x86/mm: Remove set_pages_x() and set_pages_nx() tip-bot2 for Christoph Hellwig
2019-08-26 7:55 ` [PATCH 4/5] x86: remove the unused set_memory_wt function Christoph Hellwig
2019-09-03 8:32 ` [tip: x86/mm] x86/mm: Remove the unused set_memory_wt() function tip-bot2 for Christoph Hellwig
2019-08-26 7:55 ` [PATCH 5/5] x86: remove the unused set_pages_array_wt function Christoph Hellwig
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=20190826075558.8125-1-hch@lst.de \
--to=hch@lst.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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
all inboxes | Powered by JetHome®