From: Helge Deller <deller@gmx.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
John David Anglin <dave.anglin@bell.net>,
linux-parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: Purge existing TLB entries in set_pte_at and ptep_set_wrprotect - take 2
Date: Wed, 16 Jan 2013 23:18:35 +0100 [thread overview]
Message-ID: <50F7273B.6010906@gmx.de> (raw)
In-Reply-To: <6320254.iVaF30vePD@donald.sf-tec.de>
Hi Rolf,
On 01/16/2013 10:44 PM, Rolf Eike Beer wrote:
> James Bottomley wrote:
>> On Mon, 2013-01-14 at 19:45 -0500, John David Anglin wrote:
>>> Attached is new version of patch which no longer saves and restores
>>> %sr1. Lightly tested with a GCC build
>>> and a build of Debian gtk+3.0 package.
>>
>> I can merge it with your previous changelog, but for ease of git users,
>> the accepted format is
>
>> v2: Attached is new version of patch which no longer saves and
>> restores %sr1. Lightly tested with a GCC build and a build of
>> Debian gtk+3.0 package.
>
> Do we want that to go back into stable kernels?
Short answer: Yes.
Long answer:
First we need those patches upstream - which is what did not happened yet.
Then I wanted to take a look what we can send to stable.
Helge
prev parent reply other threads:[~2013-01-16 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 0:45 [PATCH] parisc: Purge existing TLB entries in set_pte_at and ptep_set_wrprotect - take 2 John David Anglin
2013-01-15 9:05 ` James Bottomley
2013-01-16 21:44 ` Rolf Eike Beer
2013-01-16 22:18 ` Helge Deller [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=50F7273B.6010906@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.