Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Request for inclusion: commit b581a5854eee
Date: Mon, 27 Mar 2017 12:07:13 +0200	[thread overview]
Message-ID: <20170327100713.GA25373@1wt.eu> (raw)
In-Reply-To: <CAOi1vP_B7wR4B=DegSrKEpsNAeEYDy1PX6CNEO=cUnzthk=2vQ@mail.gmail.com>

On Mon, Mar 27, 2017 at 12:03:23PM +0200, Ilya Dryomov wrote:
> Hello,
> 
> Commit b581a5854eee ("libceph: don't set weight to IN when OSD is
> destroyed") was tagged with "Fixes: 930c53286977 (...)" and went into
> 4.11-rc2.  It fixes a bug in 930c53286977, which had been backported to
> many stable kernels, but it looks like no one picked it up as of now.
> 
> Is the "Fixes:" tag no longer enough to trigger a stable backport?

It's a useful hint, it's in no way a guarantee that nobody will miss it :-)
I'm queuing it for next 3.10, thanks!

Willy

  reply	other threads:[~2017-03-27 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 10:03 Request for inclusion: commit b581a5854eee Ilya Dryomov
2017-03-27 10:07 ` Willy Tarreau [this message]
2017-03-27 10:43 ` Greg KH
2017-03-27 11:38 ` Jiri Slaby

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=20170327100713.GA25373@1wt.eu \
    --to=w@1wt.eu \
    --cc=idryomov@gmail.com \
    --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