From: Mikulas Patocka <mpatocka@redhat.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: James.Bottomley@hansenpartnership.com,
linux-parisc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.4-rc7
Date: Tue, 7 Aug 2012 14:41:39 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1208071439090.6535@file.rdu.redhat.com> (raw)
In-Reply-To: <BLU0-SMTP1253492C7F871CBBDAC05297CB0@phx.gbl>
On Wed, 1 Aug 2012, John David Anglin wrote:
> On 1-Aug-12, at 9:00 PM, Mikulas Patocka wrote:
>
> >
> >
> > On Sun, 13 May 2012, John David Anglin wrote:
> >
> > > On 13-May-12, at 4:40 PM, John David Anglin wrote:
> > >
> > > > Yes, the revised change fixes the compilation error. I'll know in a
> > > > while
> > > > if
> > > > my config boots.
> > >
> > >
> > > I successfully booted 3.4-rc7 with this change on rp3440 (4 cpu smp). My
> > > build also
> > > included cache and other fixes that are being discussed on the parisc
> > > list.
> > >
> > > Dave
> >
> > Hi David
> >
> > Can I download a series of your PA-RISC patches somewhere?
> >
> > I applied this http://www.spinics.net/lists/linux-parisc/msg03352.html and
> > it improved stability for me (I had no gcc crashes since that, only
> > about two aptitude crashes).
> >
> > How stable is it for you? Do you have some random crashes or not?
>
>
> Attached are my latest patch sets for linux-stable 3.4 and 3.5 branches.
> There is no place to to download them directly. I added Jiri Kosina's
> personality fix today to the 3.5 patch set. Otherwise, they are similar.
>
> In general, stability with 3.4 has been pretty good. I just started testing
> 3.5 a couple of days ago. I went about three weeks without a random
> crash with 3.4 after I removed Al Viro's restart patch. It was causing
> problems with irq handling.
Which restart patch do you mean?
> This is on 64-bit rp3440. I have been using it to build debian unstable
> and test GCC 4.8. So, the machine gets a fair bit of exercise. In the last
> little while, it has been pretty easy to keep up with the changes in unstable.
>
> Sorry, I haven't had time to submit my changes. Some of the cache fixes
> are a bit hard to explain.
>
> Dave
> --
> John David Anglin dave.anglin@bell.net
Thanks. For me the kernel with the patch works fine - it would be nice to
break it up to smaller pieces and submit it.
Mikulas
next prev parent reply other threads:[~2012-08-07 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 2:04 Linus Torvalds
2012-05-13 19:56 ` Srivatsa S. Bhat
2012-05-13 20:08 ` John David Anglin
2012-05-13 20:28 ` Srivatsa S. Bhat
2012-05-13 20:40 ` John David Anglin
2012-05-14 0:42 ` John David Anglin
2012-05-15 17:24 ` Linus Torvalds
2012-05-15 18:29 ` Srivatsa S. Bhat
2012-05-15 18:39 ` Srivatsa S. Bhat
2012-05-15 18:42 ` Linus Torvalds
2012-05-15 18:45 ` Srivatsa S. Bhat
2012-05-15 19:04 ` James Bottomley
2012-08-02 1:00 ` Mikulas Patocka
2012-08-02 1:47 ` John David Anglin
2012-08-07 18:41 ` Mikulas Patocka [this message]
2012-08-07 19:00 ` John David Anglin
2012-05-13 20:30 ` Tobias Ulmer
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=Pine.LNX.4.64.1208071439090.6535@file.rdu.redhat.com \
--to=mpatocka@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®