From: ebiederm@xmission.com (Eric W. Biederman)
To: Guo Ren <guoren@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Brian Cain <bcain@codeaurora.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] csky: Fix function name in csky_alignment() and die()
Date: Wed, 29 Dec 2021 10:29:19 -0600 [thread overview]
Message-ID: <87o84zs7c0.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <CAJF2gTSB8rT=g_v=NAE1YmM_qNWAVj=H5mrnty-zPVXOKYCARg@mail.gmail.com> (Guo Ren's message of "Tue, 28 Dec 2021 09:46:25 +0800")
Guo Ren <guoren@kernel.org> writes:
> Hi Nathan,
>
> Three wrong parts in csky! you forgot mm/fault.c.
>
> Eric's patch seems not to cc me? Why arm64 is correct, csky is wrong. -_*!
Human frailty and the unfortunate fact I could not find a compiler for
csky, h8300, or hexagon.
Since I could not find a compiler I could not even compile test my
changes. Nor I presume could any of the automated bots.
The good thing is that Nathan caught my typo before the change made it
to Linus.
I will get these changes applied to my tree shortly.
Eric
prev parent reply other threads:[~2021-12-29 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 18:48 [PATCH 0/3] Fix build errors with do_exit() to make_task_dead() transition Nathan Chancellor
2021-12-27 18:48 ` [PATCH 1/3] hexagon: Fix function name in die() Nathan Chancellor
2021-12-27 18:48 ` [PATCH 2/3] h8300: Fix build errors from do_exit() to make_task_dead() transition Nathan Chancellor
2021-12-27 18:48 ` [PATCH 3/3] csky: Fix function name in csky_alignment() and die() Nathan Chancellor
2021-12-28 1:46 ` Guo Ren
2021-12-28 1:47 ` Guo Ren
2021-12-28 1:53 ` Guo Ren
2021-12-28 2:01 ` Guo Ren
2021-12-28 2:18 ` Nathan Chancellor
2021-12-28 2:50 ` Guo Ren
2021-12-29 16:29 ` Eric W. Biederman [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=87o84zs7c0.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=bcain@codeaurora.org \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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