From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932186AbdA0JAi (ORCPT <rfc822;w@1wt.eu>);
        Fri, 27 Jan 2017 04:00:38 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:34330 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754231AbdA0JA3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 27 Jan 2017 04:00:29 -0500
Date: Fri, 27 Jan 2017 10:00:41 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
        LKML <linux-kernel@vger.kernel.org>,
        "Jon Medhurst (Tixy)" <tixy@linaro.org>
Subject: Re: [PATCH] firmware: arm_scpi: Add hardware dependencies
Message-ID: <20170127090041.GA21991@kroah.com>
References: <20170125143200.0554ad0f@endymion>
 <d59d07a4-afaf-d475-9c57-97b141dafd27@arm.com>
 <20170125145037.14a790c4@endymion>
 <7561802d-e9d3-2b82-35dc-465c06d6d4eb@arm.com>
 <20170125151428.1a2a532f@endymion>
 <aa5c9d06-8e7c-c9ec-4cfb-987d2f625926@arm.com>
 <20170125160428.2540beb2@endymion>
 <4521295e-e1f9-f4b0-358f-6a1e421ebc8a@arm.com>
 <20170127095317.2f780a7f@endymion>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170127095317.2f780a7f@endymion>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Jan 27, 2017 at 09:53:17AM +0100, Jean Delvare wrote:
> On Wed, 25 Jan 2017 15:15:45 +0000, Sudeep Holla wrote:
> > > (...)
> > > As a side note, there's no finger-pointing implied by Fixes: tags. They
> > > are only meant to help people backporting patches, so that they know if
> > > something they backported is later fixed up. It does not imply anything
> > > regarding how serious the problem was.
> > 
> > Yes, but sometimes it's taken for stable tree
> 
> Really? I would expect that only patches tagged with "Cc:
> stable@vger.kernel.org", or explicitly sent to that list, are
> considered for stable trees. Greg, you don't pick commits for stable
> trees just because they have a "Fixes:" tag, do you?

Sometimes I do, usually because the maintainer has forgotten to put the
stable cc: (some subsystems are really bad about this), or because it
fixes a patch that was previous backported to stable.

I also take other patches that have no markings at all for stable trees,
depending on what they do, or who recommends them.  I try to scan all
commits for stuff that should be included that someone forgot to put a
stable@ cc: on.

But, just because you put a Fixes: tag, does not mean it will always go
into stable, because I do miss things at times.  If you know it should
go there, please always put the correct CC: tag.

thanks,

greg k-h