From: heiko.carstens@de.ibm.com (Heiko Carstens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 00/14] set_memory_* functions header refactor
Date: Thu, 2 Mar 2017 08:34:26 +0100 [thread overview]
Message-ID: <20170302073426.GA7265@osiris> (raw)
In-Reply-To: <1488413706-9739-1-git-send-email-labbott@redhat.com>
On Wed, Mar 01, 2017 at 04:14:52PM -0800, Laura Abbott wrote:
> Hi,
>
> This is v2 of my proposal to move set_memory_* function prototypes out of
> cacheflush.h and into their own header file. This came out of a comment
> Russell made while reviewing RODATA test cases
> http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/480855.html
> While the final result of that series was the rodata code was refactored into
> its own header file, the set_memory_* APIs are still out of place.
>
> This version refactored the common set_memory_* functions into an asm-generic
> header. s390x added some features so it can't just use the asm-generic header.
> I debated how much more to try and shove into the asm-generic version (e.g.
> stub prototypes for the ARM nommu case, set_kernel_text_*) but decided to stick
> with just the basics for this version.
>
> I split out the cacheflush.h -> set_memory.h conversions into separate patches
> to hopefully make merging easier. Worst case, the final patch to completely
> separate the two can be delayed if there are more problems found. I'd like
> for this to eventually go through the -mm tree so I'd like Acks where
> appropriate.
>
> As always, feedback appreciated.
For the s390 bits:
Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com>
prev parent reply other threads:[~2017-03-02 7:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 0:14 [PATCHv2 00/14] set_memory_* functions header refactor Laura Abbott
2017-03-02 0:14 ` [PATCHv2 01/14] treewide: Move set_memory_* functions away from cacheflush.h Laura Abbott
2017-03-02 12:07 ` Russell King - ARM Linux
2017-03-02 14:11 ` Mark Rutland
2017-03-02 0:14 ` [PATCHv2 02/14] arm: Use set_memory.h header Laura Abbott
2017-03-02 12:01 ` Russell King - ARM Linux
2017-03-02 0:14 ` [PATCHv2 03/14] arm64: " Laura Abbott
2017-03-02 14:07 ` Mark Rutland
2017-03-02 15:06 ` Catalin Marinas
2017-03-02 0:14 ` [PATCHv2 04/14] s390: " Laura Abbott
2017-03-02 0:14 ` [PATCHv2 05/14] x86: " Laura Abbott
2017-03-02 8:01 ` Ingo Molnar
2017-03-02 0:14 ` [PATCHv2 06/14] agp: " Laura Abbott
2017-03-02 0:14 ` [PATCHv2 07/14] drm: " Laura Abbott
2017-03-05 1:08 ` kbuild test robot
2017-03-02 0:15 ` [PATCHv2 08/14] intel_th: " Laura Abbott
2017-03-02 11:06 ` Alexander Shishkin
2017-03-02 0:15 ` [PATCHv2 09/14] watchdog: hpwdt: " Laura Abbott
2017-03-02 14:48 ` Guenter Roeck
2017-03-02 0:15 ` [PATCHv2 10/14] bpf: " Laura Abbott
2017-03-02 20:26 ` Daniel Borkmann
2017-03-05 3:01 ` kbuild test robot
2017-03-02 0:15 ` [PATCHv2 11/14] module: " Laura Abbott
2017-03-02 17:09 ` Jessica Yu
2017-03-02 0:15 ` [PATCHv2 12/14] PM / hibernate: " Laura Abbott
2017-03-02 0:15 ` [PATCHv2 13/14] ALSA: hda: " Laura Abbott
2017-03-02 0:15 ` [PATCHv2 14/14] treewide: Decouple cacheflush.h and set_memory.h Laura Abbott
2017-03-02 12:06 ` Russell King - ARM Linux
2017-03-02 14:12 ` Mark Rutland
2017-03-02 15:05 ` Catalin Marinas
2017-03-04 22:57 ` kbuild test robot
2017-03-05 0:03 ` kbuild test robot
2017-03-02 7:34 ` Heiko Carstens [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=20170302073426.GA7265@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-arm-kernel@lists.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).