From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Michael Buesch <mb@bu3sch.de>,
Alexey Zaytsev <zaytsev.a@protei.ru>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: bcm43xx regression in 2.6.24 (with patch)
Date: Sat, 23 Feb 2008 12:24:36 +0100 [thread overview]
Message-ID: <20080223112436.GA31304@elte.hu> (raw)
In-Reply-To: <84144f020802230318hec5fe97h84c797a56b0dd5db@mail.gmail.com>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Agreed. Alexey, did you identify a specific git commit that caused the
> regression? Can we just revert that from 2.6.24? Michael, even if
> _you're_ planning to remove bcm43xx we must not let it regress until
> it's gone.
btw., if the best answer is: "do not enable b43 and bcm43xx at once in
the .config because we messed up the dependencies and fixing it in
2.6.24-stable is unfortunately too risky", then that's a perfectly fine
answer for -stable. Then the fix would be to exclude each other in the
Kconfig space (which is not risky). But just ignoring bugreports and
NAK-ing a fix is not a valid answer.
Ingo
next prev parent reply other threads:[~2008-02-23 11:25 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 11:17 bcm43xx regression in 2.6.24 (with patch) Alexey Zaytsev
2008-02-22 14:13 ` Michael Buesch
2008-02-22 17:51 ` Gabriel C
2008-02-22 17:56 ` Michael Buesch
2008-02-22 22:10 ` Greg KH
2008-02-22 18:10 ` Alexey Zaytsev
2008-02-22 17:48 ` Michael Buesch
2008-02-22 20:06 ` Alexey Zaytsev
2008-02-22 20:12 ` Michael Buesch
2008-02-22 20:38 ` Alexey Zaytsev
2008-02-22 22:12 ` Greg KH
2008-02-22 22:45 ` Alexey Zaytsev
2008-02-23 5:48 ` Michael Buesch
2008-02-23 11:07 ` Ingo Molnar
2008-02-23 11:18 ` Pekka Enberg
2008-02-23 11:24 ` Ingo Molnar [this message]
2008-02-23 11:32 ` Alexey Zaytsev
2008-02-23 11:37 ` Pekka Enberg
2008-02-23 11:51 ` Alexey Zaytsev
2008-02-23 11:57 ` Pekka J Enberg
2008-02-23 12:17 ` Alexey Zaytsev
2008-02-23 12:23 ` Pekka Enberg
2008-02-24 14:29 ` Michael Buesch
2008-02-24 16:39 ` Alexey Zaytsev
2008-02-24 17:16 ` Michael Buesch
2008-02-25 6:16 ` Pekka J Enberg
2008-02-25 6:49 ` Greg KH
2008-02-25 6:54 ` Pekka J Enberg
2008-02-25 9:54 ` Michael Buesch
2008-02-25 12:11 ` Pekka Enberg
2008-02-25 12:19 ` Michael Buesch
2008-02-25 12:25 ` Pekka J Enberg
2008-02-25 13:00 ` Alexey Zaytsev
2008-02-25 10:23 ` Alexey Zaytsev
2008-02-25 10:38 ` Michael Buesch
2008-02-25 10:49 ` Xavier Bestel
2008-02-25 10:54 ` Michael Buesch
2008-02-23 16:05 ` Michael Buesch
2008-02-23 16:27 ` Michael Buesch
2008-02-23 16:44 ` Ingo Molnar
2008-02-23 16:50 ` Michael Buesch
2008-02-23 21:32 ` Alexey Zaytsev
2008-02-23 22:20 ` Michael Buesch
2008-02-26 20:20 ` John W. Linville
2008-02-26 21:38 ` Alexey Zaytsev
2008-02-26 22:04 ` Michael Buesch
2008-02-26 22:12 ` Alexey Zaytsev
2008-02-26 22:41 ` Michael Buesch
2008-02-28 22:03 ` Michael Buesch
2008-02-28 22:48 ` Alexey Zaytsev
2008-02-28 23:12 ` Stefan Lippers-Hollmann
2008-02-29 23:22 ` Alexey Zaytsev
2008-02-28 23:14 ` Michael Buesch
2008-02-26 22:47 ` John W. Linville
2008-02-26 23:12 ` Michael Buesch
2008-02-27 0:23 ` Alexey Zaytsev
2008-02-27 0:27 ` Michael Buesch
2008-02-27 0:32 ` Alexey Zaytsev
2008-02-27 0:43 ` Michael Buesch
2008-02-27 0:53 ` Alexey Zaytsev
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=20080223112436.GA31304@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=zaytsev.a@protei.ru \
/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