From: Wolfgang Walter <wolfgang.walter@stwm.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3.3.x: e1000 and ixgbe hang
Date: Wed, 9 May 2012 11:07:11 +0200 [thread overview]
Message-ID: <201205091107.11820.wolfgang.walter@stwm.de> (raw)
In-Reply-To: <20120508215645.GA22200@kroah.com>
Am Dienstag, 8. Mai 2012 schrieben Sie:
> On Tue, May 08, 2012 at 11:30:12PM +0200, Wolfgang Walter wrote:
> > I would be very glad if these two patches will make it into the next
> > stable 3.3:
> >
> > http://article.gmane.org/gmane.linux.drivers.e1000.devel/9948
> >
> > Dave Miller said that he will take care of it:
> >
> > http://article.gmane.org/gmane.linux.drivers.e1000.devel/9993
>
> If he said he would take care of it, why are you posting it here again?
a) Because it didn't make it into 3.3.5. The fix (for 3.3.x) is known since
2012-04-20 and I find it appropriate to remind of it after more than two
weeks.
b) To document the bug (which makes 3.3. i.e. unusable for us) and that there
are fixes in the stable mailinglist and not only in e1000-devel (especially
as it isn't a e1000 specific problem).
c) I met 2 colleague yesterday which had the same problems but didn't know
there was a fix.
c) Dave Miller is a busy man.
It's unclear how one should use new kernels if it is difficult to find known
fixes.
Regards,
--
Wolfgang Walter
Studentenwerk M�nchen
Anstalt des �ffentlichen Rechts
next parent reply other threads:[~2012-05-09 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201205082330.12831.wolfgang.walter@stwm.de>
[not found] ` <20120508215645.GA22200@kroah.com>
2012-05-09 9:07 ` Wolfgang Walter [this message]
2012-05-09 16:05 ` 3.3.x: e1000 and ixgbe hang David Miller
2012-05-09 16:57 ` Wolfgang Walter
2012-05-09 18:07 ` Greg KH
2012-05-09 19:45 ` David Miller
2012-05-09 22:59 ` Wolfgang Walter
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=201205091107.11820.wolfgang.walter@stwm.de \
--to=wolfgang.walter@stwm.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox