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: Thu, 10 May 2012 00:59:04 +0200 [thread overview]
Message-ID: <201205100059.04723.wolfgang.walter@stwm.de> (raw)
In-Reply-To: <20120509.154558.1469429813580317150.davem@davemloft.net>
On Wednesday 09 May 2012, David Miller wrote:
> From: Wolfgang Walter <wolfgang.walter@stwm.de>
> Date: Wed, 9 May 2012 18:57:13 +0200
>
> > 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 think you have no idea what goes into vetting patches for -stable.
I can imagine that very well. I wrote and manage a bunch of larger patches
against wine vanilla for us and to port them regularly to newer versions.
>
> It can take me days to put together a series, and also I time my
> -stable submissions with when Linus pulls my 'net' bug fixes into his
> tree since a part of the -stable requirements is presence in Linus's
> tree.
I know.
>
> I therefore batch, because bleeding out individual fixes one by one to
> -stable rarely, if ever, makes sense.
I understand that and as I sad it was not my intention to question that.
>
> And another part of what goes into vetting a patch is time. The
> longer a patch sits in a non-stable tree getting tested, the more
> likely any unwanted bugs and side effects will be caught before the
> patch goes into -stable.
>
> And finally I am under no obligation whatsoever to post some kind of
> status report to -stable every few days saying when I'll do this or
> that.
>
I didn't say that you should do that.
I just don't see the point why I should not send a mail to stable@. It
documented that there is a known problem in 3.3.5, the fix for it and that you
already aware of it and will take care to get it into stable. Nobody had
reported that on stable@.
I mentioned your mail not to blame you but so nobody thinks I want du submit
it directly. Everybody reading your mail I linked to could see that you wrote
it May 1st and therefor could not be in 3.3.5.
But I think it would have been good if someone (not you) had sent a mail as
early as 2012-04-20 to stable@ so that others could find the solution more
easily.
Regards,
--
Wolfgang Walter
Studentenwerk M�nchen
Anstalt des �ffentlichen Rechts
prev parent reply other threads:[~2012-05-09 22:59 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
2012-05-09 18:07 ` Greg KH
2012-05-09 19:45 ` David Miller
2012-05-09 22:59 ` Wolfgang Walter [this message]
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=201205100059.04723.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