linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Daniel Axtens <dja@axtens.net>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [RFC WIP PATCH 0/3] Your series rebased
Date: Tue, 19 Feb 2019 17:29:54 +0000 (UTC)	[thread overview]
Message-ID: <cover.1550597162.git.christophe.leroy@c-s.fr> (raw)

Hi Daniel,

Find here your series rebased on my v6. No test done, not even compiled.

Christophe

Christophe Leroy (3):
  kasan: do not open-code addr_has_shadow
  kasan: allow architectures to manage the memory-to-shadow mapping
  powerpc: KASAN for 64bit Book3E

 arch/powerpc/Kconfig                         |  1 +
 arch/powerpc/Makefile                        |  2 +
 arch/powerpc/include/asm/kasan.h             | 56 +++++++++++++++++++++++++++-
 arch/powerpc/mm/Makefile                     |  2 +
 arch/powerpc/mm/kasan/Makefile               |  1 +
 arch/powerpc/mm/kasan/kasan_init_book3e_64.c | 51 +++++++++++++++++++++++++
 include/linux/kasan.h                        |  2 +
 mm/kasan/generic.c                           |  3 +-
 mm/kasan/generic_report.c                    |  2 +-
 mm/kasan/kasan.h                             |  6 ++-
 mm/kasan/report.c                            |  6 +--
 mm/kasan/tags.c                              |  3 +-
 12 files changed, 125 insertions(+), 10 deletions(-)
 create mode 100644 arch/powerpc/mm/kasan/kasan_init_book3e_64.c

-- 
2.13.3


             reply	other threads:[~2019-02-19 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 17:29 Christophe Leroy [this message]
2019-02-19 17:29 ` [RFC WIP PATCH 1/3] kasan: do not open-code addr_has_shadow Christophe Leroy
2019-02-19 17:29 ` [RFC WIP PATCH 2/3] kasan: allow architectures to manage the memory-to-shadow mapping Christophe Leroy
2019-02-19 17:29 ` [RFC WIP PATCH 3/3] powerpc: KASAN for 64bit Book3E Christophe Leroy

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=cover.1550597162.git.christophe.leroy@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=dja@axtens.net \
    --cc=linuxppc-dev@lists.ozlabs.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).