stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net, Guenter Roeck <linux@roeck-us.net>,
	Hugh Dickins <hughd@google.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Borislav Petkov <bp@alien8.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposed stable release changes
Date: Wed, 21 Aug 2013 11:15:33 -0700	[thread overview]
Message-ID: <20130821181533.GA25438@kroah.com> (raw)
In-Reply-To: <CA+5PVA4Bf7mbB9qFWPfcX-xQDeKPoBKSjW_hF-td9sUUkFRDJQ@mail.gmail.com>

On Tue, Aug 20, 2013 at 09:03:12PM -0400, Josh Boyer wrote:
> Suspend/Resume is broken on a variety of Thinkpad T400 and T500
> machines in 3.10.  This was true with 3.10.0 afaik.  Current thinking
> is that it's related to the Intel mei/mei_me driver(s).  Blacklisting
> those seems to fix things for a number of users.  There are patches in
> 3.11-rcX, but the "fix" highlighted doesn't fix it.

I have heard of mei issues recently, but no real "this is a problem"
type thing.  There are some patches queued up for 3.12 in that area, if
they are needed earlier, that would be great for me, as a subsystem
maintainer, to know.

> I'm aware I'm reporting issues that you either already knew about or
> were already fixed.  The problem we have is that we roll out a new
> stable release and then we get bug reports for 2 weeks because not
> everyone updates as frequently as stable releases, etc.  So something
> that may seem to impact a small number of users at the time winds up
> actually impacting lots of users once it rolls out in a distro.  As
> far as I know, Fedora is possibly the only distro actually pushing
> stable release kernels out on a normal basis.  I'd love to be wrong on
> that point.

The openSUSE Tumbleweed disto also pushes out these stable kernels.  But
there's only an "estimated" 8-10 thousand users of that openSUSE
"flavor", while smaller than what Fedora has, it's better than nothing.

> In the future, if we can get the information from the end user in
> time, I'll be happy to forward issues that aren't already reported
> onwards.  Or if you still want to hear about it, I can chime in on the
> existing threads with bugzilla numbers.  I'm also willing to do a
> monthly "patches we're carrying not in stable" report if people find
> that helpful.

I would love that report, one of the things I keep asking for is for
people to send the patches that distros have that are not in stable to
me, as those obviously are things that are needed for a valid reason
that everyone should be able to benifit from.

> I'll likely be doing that within Fedora already and I'm happy to send
> it to stable@, even if those patches aren't exactly stable-rules
> matching.

If they aren't "allowed" by the current rules, I'd be interested to know
why, unless it's the "add a new feature" type thing, which makes sense
why I couldn't take them.

> We did that when kernel.org went down and it helped then, just not
> sure how much it would help now or if people care.

I care :)

thanks,

greg k-h

  parent reply	other threads:[~2013-08-21 18:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 22:40 Proposed stable release changes Greg KH
2013-08-20 22:58 ` Willy Tarreau
2013-08-20 23:12   ` Greg KH
2013-08-20 23:57     ` Guenter Roeck
2013-08-21  5:24     ` Willy Tarreau
2013-08-20 23:04 ` Nicholas A. Bellinger
2013-08-20 23:12   ` Greg KH
2013-08-20 23:11 ` Guenter Roeck
2013-08-20 23:17   ` Greg KH
2013-08-21  0:11     ` Guenter Roeck
2013-08-21  0:42       ` Greg KH
2013-08-20 23:40 ` Josh Boyer
2013-08-20 23:57   ` Greg KH
2013-08-21  0:41     ` Josh Boyer
2013-08-21  0:49       ` Greg KH
2013-08-21  1:03         ` Josh Boyer
2013-08-21  1:11           ` Guenter Roeck
2013-08-21 18:15           ` Greg KH [this message]
2013-08-21  5:38         ` Willy Tarreau
2013-08-21 13:37           ` Steven Rostedt
2013-08-21 17:23             ` Jochen Striepe
2013-08-21 17:58               ` Steven Rostedt
2013-08-21 20:07                 ` Borislav Petkov
2013-08-21 20:16                   ` Greg KH
2013-08-21 21:00                     ` Borislav Petkov
2013-08-21 13:42       ` Steven Rostedt
2013-08-21 14:17         ` Willy Tarreau
2013-08-21 14:54           ` Steven Rostedt
2013-08-24 18:45             ` Stefan Richter
2013-08-21 13:48 ` Borislav Petkov
2013-08-21 17:08   ` Greg KH
2013-08-21 18:20 ` Stephen Warren
2013-08-21 18:36   ` Linus Torvalds
2013-08-21 20:00     ` Borislav Petkov
2013-08-21 20:54       ` Tony Luck
2013-08-22  8:57         ` Borislav Petkov
2013-08-22 10:59         ` Geert Uytterhoeven
2013-08-22  0:05     ` Stephen Rothwell

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=20130821181533.GA25438@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=hughd@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).