From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Ben Collins <bcollins@debian.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ]
Date: Wed, 23 Apr 2003 16:51:22 +0200 [thread overview]
Message-ID: <20030423145122.GL820@hottah.alcove-fr> (raw)
In-Reply-To: <20030423142353.GL354@phunnypharm.org>
On Wed, Apr 23, 2003 at 10:23:53AM -0400, Ben Collins wrote:
> > While this is a reasonable explanation, we are now in rc mode, and
> > your changes are not trivial, they could introduce a big pile of
> > new bugs.
> >
> > Marcelo, please revert the latest IEEE1394 changeset entirely.
> >
> > Let's hope that things will happen differently in 2.4.22-pre :(
>
> Uh no, reverting it will just re-introduce bugs that it fixed.
Maybe, but the version prior to 2.4.21-pre7 worked pretty good
for me.
> 2.4.22-pre should have come around a long time ago. The only reason most
> of the changes in 2.4.21-pre for ieee1394 are there is because of the
> amount of time that 2.4.21-pre has been sitting around. I was trying to
> hold off most of these changes for 2.4.22-pre, but .21-pre lingered for
> so long it became unreasonable.
I entirely agree.
However, the patch we are discussing has only *6 days*. If you had
submitted it 2 months ago, there wouldn't be such problems.
[BTW: searching back the l-k archives doesn't find any occurances of
your patch. I guess you sended it directly to Marcelo...]
> Then after a long huge pause, it suddenly goes -rc. Should that leave me
> stuck? Don't think so.
Sure, you should continue development and submit a fresh new version
ready to be tested in 2.4.22-pre1/pre2.
As for 2.4.21, well, we want something pretty well tested. Will this
be the case with your new mega-patch ? I don't think so. The safest
is to go back to a version which worked. At least the bugs of that
version are known, which is not the case for the new version.
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
next prev parent reply other threads:[~2003-04-23 14:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 12:29 Tony Spinillo
2003-04-23 12:53 ` Stelian Pop
2003-04-23 13:01 ` Ben Collins
2003-04-23 13:22 ` Stelian Pop
2003-04-23 13:32 ` Ben Collins
2003-04-23 13:46 ` Ben Collins
2003-04-23 13:58 ` Stelian Pop
2003-04-23 13:54 ` Ben Collins
2003-04-23 14:21 ` Stelian Pop
2003-04-23 14:23 ` Ben Collins
2003-04-23 14:51 ` Stelian Pop [this message]
2003-04-23 14:44 ` Ben Collins
2003-04-23 14:48 ` Ben Collins
2003-04-23 15:29 ` Stelian Pop
2003-04-23 19:13 ` Marcelo Tosatti
2003-04-23 19:05 ` Ben Collins
2003-04-23 19:27 ` Marcelo Tosatti
2003-04-23 20:20 ` Stelian Pop
2003-04-23 20:24 ` Ben Collins
2003-04-23 20:42 ` Stelian Pop
2003-04-26 8:29 ` The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ] Stelian Pop
2003-04-26 14:34 ` Ben Collins
2003-04-26 16:10 ` Stelian Pop
2003-04-26 16:12 ` Ben Collins
2003-04-26 17:00 ` Stelian Pop
2003-04-26 16:59 ` Ben Collins
2003-04-26 14:40 ` Ben Collins
2003-04-26 16:23 ` Stelian Pop
2003-04-26 16:25 ` Ben Collins
2003-04-26 17:15 ` Stelian Pop
2003-04-24 21:44 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Bill Davidsen
2003-04-24 21:41 ` Ben Collins
2003-04-25 18:06 ` Bill Davidsen
2003-04-25 18:16 ` Ben Collins
2003-04-26 10:36 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 18:47 Linux 2.4.21-rc1 Marcelo Tosatti
2003-04-23 7:59 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Stelian Pop
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=20030423145122.GL820@hottah.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®