From: Marcel Holtmann <marcel@holtmann.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
David Miller <davem@davemloft.net>,
johannes@sipsolutions.net, linville@tuxdriver.com,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344
Date: Wed, 04 Nov 2009 00:36:28 +0900 [thread overview]
Message-ID: <1257262588.3420.79.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.01.0911030719430.31845@localhost.localdomain>
Hi Linus,
> > and can we please stop jumping the gun here and going past the subsystem
> > maintainers. I think this happens a little bit too much lately.
>
> NO!
>
> Quite frankly, I'm very unhappy indeed with the maintainers when it comes
> to this bug:
>
> - it was introduced after -rc5
>
> - it's been bisected by multiple people
>
> - I've seen one of the encounters with a person who bisected it, and the
> author of the buggy commit just wanted "more information" after having
> been told that small commit causes lockups.
>
> In other words - the LAST thing we should do is to pat the subsystem
> maintainers on the back and say "good job".
>
> The fact is, when somebody reports a major bug that is fixed by a revert,
> then I shoudl probably revert _more_ eagerly rather than less!
>
> And subsystem maintainers should jump on it, not wait several days.
no questions that it needs fixed, I agree with you. However just blindly
reverting something, because it fixes it for one or two people, might
have side effects that causes more problems than the revert would
actually fix. In this case, let at least give John or Johannes a chance
to comment on it.
I do love the fact that it gets bisected down to one particular commit.
That is great and thanks to the people who did that, but let the
subsystem maintainers know and then have them either provide a fix or
revert it by them. Sometimes it might take more than one day. And lets
be honest here, Johannes is one of the most responsive persons when it
comes to wireless bugs.
Regards
Marcel
next prev parent reply other threads:[~2009-11-03 15:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 5:31 Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344 Dmitry Torokhov
2009-11-03 6:49 ` David Miller
2009-11-03 6:52 ` Dmitry Torokhov
2009-11-03 7:16 ` Marcel Holtmann
2009-11-03 7:44 ` Johannes Berg
2009-11-03 8:22 ` Dmitry Torokhov
2009-11-03 8:31 ` Johannes Berg
2009-11-03 8:47 ` Dmitry Torokhov
2009-11-03 8:57 ` Johannes Berg
2009-11-03 15:29 ` Marcel Holtmann
2009-11-03 15:38 ` Linus Torvalds
2009-11-05 19:19 ` Pavel Machek
2009-11-03 15:31 ` Linus Torvalds
2009-11-04 6:34 ` Andrew Morton
2009-11-04 8:41 ` David Miller
2009-11-04 15:23 ` Andrew Morton
2009-11-04 16:32 ` David Miller
2009-11-03 15:26 ` Linus Torvalds
2009-11-03 15:36 ` Marcel Holtmann [this message]
2009-11-03 15:43 ` Linus Torvalds
2009-11-03 16:07 ` Linus Torvalds
2009-11-03 16:08 ` Marcel Holtmann
2009-11-03 16:23 ` Linus Torvalds
2009-11-03 16:37 ` Linus Torvalds
2009-11-03 16:44 ` Marcel Holtmann
2009-11-03 16:59 ` Linus Torvalds
2009-11-03 16:29 ` Ingo Molnar
2009-11-03 16:49 ` Marcel Holtmann
2009-11-03 17:04 ` Ingo Molnar
2009-11-03 17:24 ` Luis R. Rodriguez
2009-11-03 17:37 ` Linus Torvalds
2009-11-03 17:49 ` Dmitry Torokhov
2009-11-03 17:55 ` Luis R. Rodriguez
2009-11-03 15:54 ` Zdenek Kabelac
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=1257262588.3420.79.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=torvalds@linux-foundation.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