From: devzero@web.de
To: akpm@linux-foundation.org, kenchen@google.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-git11: BUG in loop.ko
Date: Fri, 11 May 2007 09:40:20 +0200 [thread overview]
Message-ID: <1783707000@web.de> (raw)
>+ modprobe loop max_loop=128
>loop: the max_loop option is obsolete and will be removed in March 2008
looks like fc6 already contains that "remove artificial software max_loop limit" patch ?
what about mainline - will it be in 2.6.22, as andrew "estimated" when the patch showed up?
i`m asking, because i`m just curious - seems that this was put "on hold" - so someone confirm we need to wait for 2.6.23 or later?
sorry for the noise
roland
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
next reply other threads:[~2007-05-11 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 7:40 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-09 23:52 2.6.21-git11: BUG in loop.ko Jeremy Fitzhardinge
2007-05-10 0:05 ` Andrew Morton
2007-05-10 0:20 ` Jeremy Fitzhardinge
2007-05-10 7:39 ` Alexey Dobriyan
2007-05-10 10:33 ` Alexey Dobriyan
2007-05-11 6:10 ` Ken Chen
2007-05-11 15:09 ` Jeremy Fitzhardinge
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=1783707000@web.de \
--to=devzero@web.de \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@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.