From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Helge Deller <deller@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [GIT PULL] parisc updates for v3.10
Date: Mon, 13 May 2013 23:53:29 +0200 [thread overview]
Message-ID: <2654532.supg57YsM8@donald.sf-tec.de> (raw)
In-Reply-To: <20130513204843.GA1858@p100.box>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
> Helge Deller (2):
> parisc: make default cross compiler search more robust (v3)
Needs CC:stable as without this building 3.9.x is not possible in some
configurations.
> John David Anglin (1):
> parisc: fix SMP races when updating PTE and TLB entries in entry.S
Possibly also this as it's a bugfix, but Dave is the one who may be judge how
"clear" it is.
The same is probably true for these from the first round of updates:
John David Anglin (2):
parisc: use long branch in fork_like macro
Mike Frysinger (1):
parisc: fix NATIVE set up in build
While I _really_ appreciate the speedup that recently happened to the parisc
development recently I would also appreciate if we can can finally get the
bugfix parts of that into stable kernels so we have the non-development tree
buildable and working without the need to backport all those stuff by hand.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-05-13 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:48 [GIT PULL] parisc updates for v3.10 Helge Deller
2013-05-13 21:53 ` Rolf Eike Beer [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 21:39 Helge Deller
2013-05-07 22:11 Helge Deller
2013-05-08 1:37 ` Stephen Rothwell
2013-05-09 20:31 ` Helge Deller
2013-05-10 0:15 ` Stephen Rothwell
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=2654532.supg57YsM8@donald.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.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