From: Nikita Danilov <Nikita@Namesys.COM>
To: Paul Wagland <paul@wagland.net>
Cc: Domenico Andreoli <cavok@libero.it>,
reiserfs-list@namesys.com,
Linux mailing list SCSI <linux-scsi@vger.kernel.org>,
Atul Mukker <atulm@lsil.com>, Hans Reiser <reiser@namesys.com>,
Linux mailing list kernel <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 and megaraid problems with debian 2.6.5
Date: Wed, 14 Apr 2004 17:09:59 +0400 [thread overview]
Message-ID: <16509.14375.539110.986025@laputa.namesys.com> (raw)
In-Reply-To: <6699459A-8E10-11D8-A41D-000A95CD704C@wagland.net>
Paul Wagland writes:
>
> On Apr 14, 2004, at 11:05, Domenico Andreoli wrote:
>
> > [ bringing this also on reiserfs ml, a great place for this kind
> > of posts. this is also the reason of the full quoting. sorry ]
>
> Thanks ;-)
>
> >> I am using the debian prepared kernel with the debian reiser4 patch. I
> >> made a cursory examination of the patch, and it appears to correlate
> >> fairly closely with the patch from the namesys site.
> >
> > you forgot to specify version of the patch you are talking about,
> > currently debian provides two versions. anyway i suppose you are
> > talking
> > about version 20040326-2, aren't you?
>
> Yes, that is correct.
>
> >> If I can help debug this situation (I am probably the only person
> >> trying this combination :-) please let me know how I should go about
> >> it.
Is there anything in the logs?
[...]
>
> Cheers,
> Paul
Nikita.
next prev parent reply other threads:[~2004-04-14 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 6:51 Paul Wagland
2004-04-14 9:05 ` Domenico Andreoli
2004-04-14 12:36 ` Paul Wagland
2004-04-14 13:09 ` Nikita Danilov [this message]
2004-04-14 13:25 ` Paul Wagland
2004-04-14 23:59 ` Paul Wagland
2004-04-18 22:36 ` reiser4 and megaraid problems with debian 2.6.5 (*solved*) Paul Wagland
2004-04-14 15:13 ` reiser4 and megaraid problems with debian 2.6.5 Hans Reiser
2004-04-14 15:37 ` Paul Wagland
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=16509.14375.539110.986025@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=atulm@lsil.com \
--cc=cavok@libero.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=paul@wagland.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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®