From: "Helge Deller" <deller@gmx.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>, deller@gmx.de
Cc: dave.anglin@bell.net, James.Bottomley@hansenpartnership.com,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH] parisc: fixes and cleanups in page cache flushing (1/4)
Date: Mon, 04 Feb 2013 16:24:56 +0100 [thread overview]
Message-ID: <20130204152456.294020@gmx.net> (raw)
In-Reply-To: <777a626d6eff1b2a6194dcfa6a8ad313@sf-mail.de>
> Von: Rolf Eike Beer <eike-kernel@sf-tec.de>
> Helge Deller wrote:
> > This is the first patch in a series of 4, with which the page cache
> > flushing of
> > parisc will gets fixed and enhanced. This even fixes the nasty
> > "minifail" bug
> > (http://wiki.parisc-linux.org/TestCases?highlight=%28minifail%29)
> > which
> > prevented parisc to stay an official debian port. Basically the
> > flush in
> > copy_user_page together with the TLB patch from commit
> > 7139bc1579901b53db7e898789e916ee2fb52d78 is what fixes the minifail
> > bug.
>
> Is this series expected to fix the thread related problems I see in the
> git testsuite?
I expect so, if not, please let us know!
If you want to test yourself, you may check out my "testing" branch from parisc-linux.git which includes all necessary patches:
https://git.kernel.org/?p=linux/kernel/git/deller/parisc-linux.git;a=shortlog;h=refs/heads/testing
Helge
next prev parent reply other threads:[~2013-02-04 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 22:59 [PATCH] parisc: fixes and cleanups in page cache flushing (1/4) Helge Deller
2013-02-03 23:04 ` Helge Deller
2013-02-04 6:42 ` Matt Turner
2013-02-04 8:35 ` Rolf Eike Beer
2013-02-04 15:24 ` Helge Deller [this message]
2013-02-04 16:37 ` Helge Deller
2013-02-04 17:11 ` John David Anglin
2013-02-04 17:57 ` Rolf Eike Beer
2013-02-04 18:36 ` John David Anglin
2013-03-03 11:38 ` Mike Frysinger
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=20130204152456.294020@gmx.net \
--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.