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
Date: Fri, 27 Jan 2017 10:00:41 +0100 [thread overview]
Message-ID: <20170127090041.GA21991@kroah.com> (raw)
In-Reply-To: <20170127095317.2f780a7f@endymion>
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
next prev parent reply other threads:[~2017-01-27 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 13:32 [PATCH] firmware: arm_scpi: Add hardware dependencies Jean Delvare
2017-01-25 13:38 ` Sudeep Holla
2017-01-25 13:50 ` Jean Delvare
2017-01-25 13:56 ` Sudeep Holla
2017-01-25 14:14 ` Jean Delvare
2017-01-25 14:20 ` Sudeep Holla
2017-01-25 15:04 ` Jean Delvare
2017-01-25 15:15 ` Sudeep Holla
2017-01-27 8:53 ` Jean Delvare
2017-01-27 9:00 ` Greg KH [this message]
2017-01-27 14:22 ` Sudeep Holla
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=20170127090041.GA21991@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tixy@linaro.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