From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2/2 v2] MIPS: Close races in TLB modify handlers.
Date: Fri, 22 Jul 2011 11:11:17 +0100 [thread overview]
Message-ID: <20110722101117.GA21860@linux-mips.org> (raw)
In-Reply-To: <20110721135525.GB27341@linux-mips.org>
On Thu, Jul 21, 2011 at 02:55:25PM +0100, Ralf Baechle wrote:
> Looks good and nobody else has complained but backporting to <= 2.6.37 is
> gonna be ugly. I either have to resolve huge conflicts or alternatively
> backport tons of other tlbex.c patches. The latter is less risky and
> time consuming and will provide additional benefit so I'll do it. Just
> be prepared for a storm on the linux-git list.
It also broke the build for the !defined(CONFIG_MIPS_PGD_C0_CONTEXT) case.
Ralf
next prev parent reply other threads:[~2011-07-22 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 23:34 [PATCH 1/2] MIPS: Add uasm UASM_i_SRL_SAFE macro David Daney
2011-07-05 23:34 ` [PATCH 2/2 v2] MIPS: Close races in TLB modify handlers David Daney
2011-07-21 13:55 ` Ralf Baechle
2011-07-22 10:11 ` Ralf Baechle [this message]
2011-07-27 7:06 ` Ralf Baechle
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=20110722101117.GA21860@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=david.daney@cavium.com \
--cc=linux-mips@linux-mips.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