From: Wolfgang Walter <wolfgang.walter@stwm.de>
To: David Miller <davem@davemloft.net>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 3.3.x: e1000 and ixgbe hang
Date: Wed, 9 May 2012 18:57:13 +0200 [thread overview]
Message-ID: <201205091857.14406.wolfgang.walter@stwm.de> (raw)
In-Reply-To: <20120509.120546.788906941073754076.davem@davemloft.net>
Am Mittwoch, 9. Mai 2012 schrieben Sie:
> From: Wolfgang Walter <wolfgang.walter@stwm.de>
> Date: Wed, 9 May 2012 11:07:11 +0200
>
> > c) Dave Miller is a busy man.
>
> Therefore pinging me on crap like this makes me a more busy man, so
> don't do it, unless you want it to take even longer for me to get
> to it.
I don't understand why you are so unfriendly.
I didn't sent you any mail nor did I complain to you. If you read my first
mail on this issue then you will see that.
But when we are at it: I think that when a bug in a stable kernel is found and
the final fix is known it is bad practice to hord that patch till submission
without letting stable@ know about it. I don't mean that the patch should go
into the stable tree immediately. Of course it makes sense to wait some time
to see if it works in Linus' tree. But why should other people waste their
time hunting a bug already solved? And why deny people the fix?
Regards,
--
Wolfgang Walter
Studentenwerk M�nchen
Anstalt des �ffentlichen Rechts
next prev parent reply other threads:[~2012-05-09 16:57 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 ` 3.3.x: e1000 and ixgbe hang Wolfgang Walter
2012-05-09 16:05 ` David Miller
2012-05-09 16:57 ` Wolfgang Walter [this message]
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=201205091857.14406.wolfgang.walter@stwm.de \
--to=wolfgang.walter@stwm.de \
--cc=davem@davemloft.net \
--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