From: Guo Ren <guoren@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
Guo Ren <ren_guo@c-sky.com>, Arnd Bergmann <arnd@arnd.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH V2 2/4] csky: Add new asid lib code from arm
Date: Fri, 21 Jun 2019 19:05:40 +0800 [thread overview]
Message-ID: <CAJF2gTQ0xQtQY1t-g9FgWaxfDXppMkFooCQzTFy7+ouwUfyA6w@mail.gmail.com> (raw)
In-Reply-To: <2c6acec4-07b7-b214-9eeb-964dc3a0d632@arm.com>
Sorry, I forgot delete arm's. It's mistake, no change arm64 file.
On Fri, Jun 21, 2019 at 6:10 PM Julien Grall <julien.grall@arm.com> wrote:
>
> Hi,
>
> On 21/06/2019 10:39, guoren@kernel.org wrote:
> > Signed-off-by: Guo Ren <ren_guo@c-sky.com>
> > Cc: Arnd Bergmann <arnd@arnd.de>
> > Cc: Julien Grall <julien.grall@arm.com>
> > ---
> > arch/arm64/lib/asid.c | 9 ++-
>
> This change should be in a separate e-mail with the Arm64 maintainers in CC.
>
> But you seem to have a copy of the allocator in csky now. So why do you need to
> modify arm64/lib/asid.c here?
>
> Cheers,
>
> --
> Julien Grall
--
Best Regards
Guo Ren
ML: https://lore.kernel.org/linux-csky/
next prev parent reply other threads:[~2019-06-21 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 9:39 [PATCH V2 0/4] csky: Use generic asid function from arm guoren
2019-06-21 9:39 ` [PATCH V2 1/4] csky: Revert mmu ASID mechanism guoren
2019-06-21 9:39 ` [PATCH V2 2/4] csky: Add new asid lib code from arm guoren
2019-06-21 10:10 ` Julien Grall
2019-06-21 11:05 ` Guo Ren [this message]
2019-06-21 9:39 ` [PATCH V2 3/4] csky: Use generic asid algorithm to implement switch_mm guoren
2019-06-21 9:39 ` [PATCH V2 4/4] csky: Improve tlb operation with help of asid guoren
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=CAJF2gTQ0xQtQY1t-g9FgWaxfDXppMkFooCQzTFy7+ouwUfyA6w@mail.gmail.com \
--to=guoren@kernel.org \
--cc=Catalin.Marinas@arm.com \
--cc=arnd@arnd.de \
--cc=arnd@arndb.de \
--cc=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ren_guo@c-sky.com \
--cc=will.deacon@arm.com \
/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).