From: Ralf Baechle <ralf@linux-mips.org>
To: Huacai Chen <chenhc@lemote.com>
Cc: "Paul Burton" <paul.burton@imgtec.com>,
"Chen Jie" <chenj@lemote.com>,
"Linux MIPS Mailing List" <linux-mips@linux-mips.org>,
王锐 <wangr@lemote.com>
Subject: Re: [PATCH] Not preempt in CP1 exception handling
Date: Fri, 1 Aug 2014 18:48:03 +0200 [thread overview]
Message-ID: <20140801164803.GA17520@linux-mips.org> (raw)
In-Reply-To: <CAAhV-H4PbCLam5jdUjCdn9X9+pL6HR5=8wT_6TPWMt31qv4gMA@mail.gmail.com>
On Mon, Jul 14, 2014 at 10:22:47AM +0800, Huacai Chen wrote:
> What do you think about? If you also prefer to totally remove the
> BUG_ON(), I will send a new patch.
I agree, removing the BUG_ON() is the right way.
Ralf
next prev parent reply other threads:[~2014-08-01 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 3:06 [PATCH] MIPS: Don't BUG_ON(!is_fpu_owner()) in do_ade() when preemptible Huacai Chen
2014-07-11 3:14 ` [PATCH] Not preempt in CP1 exception handling chenj
2014-07-11 3:13 ` Chen Jie
2014-07-11 15:56 ` Paul Burton
2014-07-11 15:56 ` Paul Burton
2014-07-11 23:28 ` Chen Jie
2014-07-12 9:10 ` Huacai Chen
2014-07-12 9:30 ` Paul Burton
2014-07-14 2:22 ` Huacai Chen
2014-08-01 16:48 ` Ralf Baechle [this message]
2014-08-19 15:56 ` Chen Jie
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=20140801164803.GA17520@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=chenhc@lemote.com \
--cc=chenj@lemote.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=wangr@lemote.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