From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: HongJieDeng <deng.hongjie@h3c.com>
Cc: paulburton@kernel.org, chenhc@lemote.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
liulichao@loongson.cn, denghongjie@h3c.com
Subject: Re: [PATCH] MIPS: Support large stack.
Date: Fri, 5 Mar 2021 08:20:07 +0100 [thread overview]
Message-ID: <20210305072007.GA5022@alpha.franken.de> (raw)
In-Reply-To: <20210305031257.14936-1-deng.hongjie@h3c.com>
On Fri, Mar 05, 2021 at 11:12:57AM +0800, HongJieDeng wrote:
> From: Hongjie Deng <deng.hongjie@h3c.com>
>
> We need more stack space, xori/ori no longer apply when
> _THREAD_MASK exceeds 16 bits
who is we and why do need more ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-03-05 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 3:12 [PATCH] MIPS: Support large stack HongJieDeng
2021-03-05 6:59 ` Jiaxun Yang
2021-03-05 7:20 ` Thomas Bogendoerfer [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=20210305072007.GA5022@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=deng.hongjie@h3c.com \
--cc=denghongjie@h3c.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liulichao@loongson.cn \
--cc=paulburton@kernel.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).