From: Jake Maciejewski <maciejej@msoe.edu>
To: "Artur Makówka" <juice@ursynow.2a.pl>
Cc: reiserfs-list@namesys.com
Subject: Re: latest 2.6.13 reiser4 patch
Date: Sat, 01 Oct 2005 14:50:22 -0500 [thread overview]
Message-ID: <1128196222.9989.32.camel@gentoo> (raw)
In-Reply-To: <002501c5c6b7$92e5dda0$0300a8c0@JUICE1>
On Sat, 2005-10-01 at 20:40 +0200, Artur Makówka wrote:
> >> Will it work also with 2.6.13.2 kernel ? or is it only for 2.6.13 ( or
> >> 2.6.13.1 )
> >>
> >> i couldnt find any information about this on page, and i want to be
> >> sure...
> >
> >I used it fine with 2.6.13.2... but my wireless card isn't supported
> >there. (it's been included in 2.6.14x, so it was never patches against
> >2.6.13.. I tried backporting my wireless driver but there were a lot
> >of changes in both directions). The patch also applies cleanly
> >against 2.6.14-rc1/2 but 2.6.14-rc1/2 panic on initrd uncompress for
> >me, and I can't troubleshoot it because the backtrace scrolls my
> >screen and I can't do a serial console on my laptop. :(
> >
> >In any case I tested reiser4 out some on 13.2, and the only bug I hit
> >was a panic on unmount.
>
> but is there some official statment about using 2.6.x reiser4 patches with
> 2.6.x.x kernels? i mean, does patch called reiser 4 2.6.13 patch is also
> intended to work with 2.6.13.2 for example or only with 2.6.13 ?
2.6.x.y patches are obvious security or bug fixes that aren't supposed
to introduce new bugs. I'm in no position to make an official statement,
but until the development process changes again, 2.6.x reiser4 patches
should always work on 2.6.x.y versions.
--
Jake Maciejewski <maciejej@msoe.edu>
next prev parent reply other threads:[~2005-10-01 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 22:07 latest 2.6.13 reiser4 patch Artur Makówka
2005-09-30 20:20 ` Gregory Maxwell
2005-10-01 18:40 ` Artur Makówka
2005-10-01 18:57 ` Gregory Maxwell
2005-10-01 19:50 ` Jake Maciejewski [this message]
2005-10-03 6:25 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 20:04 Artur Makówka
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=1128196222.9989.32.camel@gentoo \
--to=maciejej@msoe.edu \
--cc=juice@ursynow.2a.pl \
--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 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.