From: Brian Norris <computersforpeace@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Francis Moreau <francis.moro@gmail.com>,
stable@vger.kernel.org, linux-pm@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 3.10.y+] PM / sleep: Use valid_state() for platform-dependent sleep states only
Date: Fri, 5 Sep 2014 15:45:09 -0700 [thread overview]
Message-ID: <20140905224509.GF18411@ld-irv-0074> (raw)
In-Reply-To: <20140905223626.GA2376@kroah.com>
On Fri, Sep 05, 2014 at 03:36:26PM -0700, Greg Kroah-Hartman wrote:
> > > If they apply cleanly, then just list the git commit ids, and I can take
> > > care of the rest.
> >
> > OK. Is this a policy that should be documented? AIUI, we have a few
> > options:
> >
> > 1. Include 'Cc: stable@vger.kernel.org' in the original commit that
> > gets to Linus
> >
> > 2. Send an email to stable@vger.kernel.org that just contains the
> > commit IDs, after they've made it to Linus
> >
> > 3. Send patches to stable@vger.kernel.org, if backporting is not
> > trivial
> >
> > #1 is most common, and #2 seems like it would handle most of what misses
> > #1. #3 seems inferior, whenever #2 would suffice. But #2 is not in
> > stable_kernel_rules.txt.
>
> I always gladly take patches to that .txt file if you wish to make it
> clearer.
I was interested in whether I had my facts straight before trying to
document them. I'll take your response to mean I'm not far off base, so
I'll take a stab at patching the file.
Thanks,
Brian
prev parent reply other threads:[~2014-09-05 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 1:02 [stable -3.14] PM backports for pm_test / CONFIG_PM_DEBUG Brian Norris
2014-09-04 19:40 ` Rafael J. Wysocki
2014-09-04 21:14 ` Brian Norris
2014-09-04 21:21 ` [PATCH 3.10.y+] PM / sleep: Use valid_state() for platform-dependent sleep states only Brian Norris
2014-09-05 6:29 ` Francis Moreau
2014-09-05 7:45 ` Brian Norris
2014-09-05 14:52 ` Francis Moreau
2014-09-05 21:47 ` Greg Kroah-Hartman
2014-09-05 22:08 ` Brian Norris
2014-09-05 22:36 ` Greg Kroah-Hartman
2014-09-05 22:45 ` Brian Norris [this message]
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=20140905224509.GF18411@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=francis.moro@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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