From: Michael Ellerman <mpe@ellerman.id.au>
To: christophe leroy <christophe.leroy@c-s.fr>,
Daniel Axtens <dja@axtens.net>,
aneesh.kumar@linux.ibm.com, bsingharora@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, kasan-dev@googlegroups.com
Subject: Re: [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory
Date: Mon, 18 Feb 2019 20:14:32 +1100 [thread overview]
Message-ID: <87d0npqwzr.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <252ac94f-1fd6-8df1-9dd3-95ea3d68b67e@c-s.fr>
christophe leroy <christophe.leroy@c-s.fr> writes:
> Le 15/02/2019 à 01:04, Daniel Axtens a écrit :
>> In preparation for adding ppc64 implementations, break out the
>> code into its own subdirectory.
>
> That's not a bad idea, arch/powerpc/mm is rather messy with lot of
> subarch stuff.
I'm always happy to have more directories with more focused content.
cheers
next prev parent reply other threads:[~2019-02-18 9:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:04 [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 1/5] kasan: do not open-code addr_has_shadow Daniel Axtens
2019-02-15 0:12 ` Andrew Donnellan
2019-02-15 8:21 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 2/5] kasan: allow architectures to manage the memory-to-shadow mapping Daniel Axtens
2019-02-15 6:35 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 3/5] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2019-02-15 8:25 ` Dmitry Vyukov
2019-02-17 12:05 ` christophe leroy
2019-02-18 6:13 ` Daniel Axtens
2019-02-25 14:01 ` Christophe Leroy
2019-02-26 0:14 ` Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory Daniel Axtens
2019-02-15 0:24 ` Andrew Donnellan
2019-02-17 16:29 ` christophe leroy
2019-02-18 9:14 ` Michael Ellerman [this message]
2019-02-18 12:27 ` Christophe Leroy
2019-02-19 0:44 ` Michael Ellerman
2019-02-15 0:04 ` [RFC PATCH 5/5] powerpc: KASAN for 64bit Book3E Daniel Axtens
2019-02-15 8:28 ` Dmitry Vyukov
2019-02-19 6:37 ` Daniel Axtens
2019-02-17 14:06 ` christophe leroy
2019-02-18 19:26 ` Christophe Leroy
2019-02-19 0:14 ` Daniel Axtens
2019-02-15 16:39 ` [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Christophe Leroy
2019-02-17 6:34 ` Balbir Singh
2019-02-19 6:35 ` Daniel Axtens
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=87d0npqwzr.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=dja@axtens.net \
--cc=kasan-dev@googlegroups.com \
--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).