From: Hans Reiser <reiser@namesys.com>
To: Andi Kleen <ak@suse.de>
Cc: "David S. Miller" <davem@redhat.com>,
alan@lxorguk.ukuu.org.uk, willy@debian.org, thunder7@xs4all.nl,
parisc-linux@lists.parisc-linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [parisc-linux] documented Oops running big-endian reiserfs on parisc architecture
Date: Mon, 03 Sep 2001 14:48:24 +0400 [thread overview]
Message-ID: <3B935FF8.935244CE@namesys.com> (raw)
In-Reply-To: <20010903002514.X5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel> <E15dghq-0000bZ-00@the-village.bc.nu.suse.lists.linux.kernel> <oup66b0zq9j.fsf@pigdrop.muc.suse.de> <20010903.011530.62340995.davem@redhat.com> <20010903104105.A3398@gruyere.muc.suse.de>
Ok, so the sum of this is that Jeff's patches work on the platforms he wrote
them for, and we need one more fix for PA-RISC.
So, we can reasonably send Jeff's patches to Linus, and test and then put the
PA-RISC patch into the AC tree, any disagreement?
Hans
next prev parent reply other threads:[~2001-09-03 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010903002514.X5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
[not found] ` <E15dghq-0000bZ-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-09-03 7:29 ` [parisc-linux] documented Oops running big-endian reiserfs on parisc architecture Andi Kleen
2001-09-03 8:15 ` David S. Miller
2001-09-03 8:41 ` Andi Kleen
2001-09-03 10:48 ` Hans Reiser [this message]
2001-09-03 14:31 ` Matthew Wilcox
2001-09-03 15:44 ` Horst von Brand
2001-09-02 8:55 thunder7
2001-09-02 14:00 ` [parisc-linux] " Matthew Wilcox
2001-09-02 23:04 ` David S. Miller
2001-09-02 23:25 ` Matthew Wilcox
2001-09-02 23:26 ` David S. Miller
2001-09-02 23:31 ` Alan Cox
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=3B935FF8.935244CE@namesys.com \
--to=reiser@namesys.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=thunder7@xs4all.nl \
--cc=willy@debian.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