linux-kernel - Re: [PATCH] firmware: arm_scpi: Add hardware dependencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170127090041.GA21991@kroah.com>
Date:   Fri, 27 Jan 2017 10:00:41 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Jean Delvare <jdelvare@...e.de>
Cc:     Sudeep Holla <sudeep.holla@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        "Jon Medhurst (Tixy)" <tixy@...aro.org>
Subject: Re: [PATCH] firmware: arm_scpi: Add hardware dependencies

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@...r.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