From: Thomas Backlund <tmb@mandriva.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: David Miller <davem@davemloft.net>,
"stable@kernel.org" <stable@kernel.org>,
"gregkh@suse.de" <gregkh@suse.de>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [33-stable regression ssb/broadcom]
Date: Mon, 13 Sep 2010 23:34:10 +0300 [thread overview]
Message-ID: <4C8E8AC2.2030201@mandriva.org> (raw)
In-Reply-To: <20100913193647.GD4052@tuxdriver.com>
John W. Linville skrev 13.9.2010 22:36:
> On Mon, Sep 13, 2010 at 12:23:29PM -0700, David Miller wrote:
>> From: Thomas Backlund<tmb@mandriva.org>
>> Date: Mon, 13 Sep 2010 20:38:26 +0300
>>
>>> In Mandriva 2010.1 we noticed that 2.6.33.7 broke ssb/Broadcom lan for
>>> several users...
>>>
>>> Issue is tracked at:
>>> https://qa.mandriva.com/show_bug.cgi?id=60968
>>>
>>> Reverting the commit restores a working lan.
>>>
>>> The offending commit is:
>>
>> Please always CC: netdev on networking reports, otherwise you are
>> very unlikely to get any experts looking into your issue.
>
> IIRC, there was a bad patch that got sent for the 2.6.33.y series.
> I thought it had been reverted or fixed already?
>
Nope.
It got added in 2.6.33.7
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=commit;h=6fb037c2ed8378c7ab0c1e00536ba6b2a866503e
--
Thomas
next prev parent reply other threads:[~2010-09-13 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 17:38 [33-stable regression ssb/broadcom] Thomas Backlund
2010-09-13 17:42 ` Greg KH
2010-09-13 17:50 ` Thomas Backlund
2010-09-13 19:23 ` David Miller
2010-09-13 19:36 ` John W. Linville
2010-09-13 20:34 ` Thomas Backlund [this message]
2010-09-13 20:41 ` Thomas Backlund
2010-09-13 21:01 ` Greg KH
2010-09-15 9:54 ` Thomas Backlund
2010-09-15 10:02 ` Krzysztof Olędzki
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=4C8E8AC2.2030201@mandriva.org \
--to=tmb@mandriva.org \
--cc=Larry.Finger@lwfinger.net \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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.