From: Greg KH <greg@kroah.com>
To: William Dauchy <william@gandi.net>
Cc: "David E. Box" <david.e.box@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"Ingo Molnar" <mingo@kernel.org>,
"“stable@vger.kernel.org”" <stable@vger.kernel.org>
Subject: Re: stable fix for IOSF in Kconfig
Date: Thu, 2 Jul 2015 06:07:19 -0700 [thread overview]
Message-ID: <20150702130719.GA5256@kroah.com> (raw)
In-Reply-To: <20150702092410.GA15144@gandi.net>
On Thu, Jul 02, 2015 at 11:24:10AM +0200, William Dauchy wrote:
> On Jun29 15:53, Greg KH wrote:
> > As it doesn't fix a real bug, I'll not apply it, thanks.
>
> agreed; but the first one is targeted for future stables releases,
> right?
The first "what"? There is no context here :(
next prev parent reply other threads:[~2015-07-02 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 12:27 stable fix for IOSF in Kconfig William Dauchy
2015-05-20 15:59 ` Greg KH
2015-05-20 16:04 ` William Dauchy
2015-06-29 22:53 ` Greg KH
2015-07-02 9:24 ` William Dauchy
2015-07-02 13:07 ` Greg KH [this message]
2015-07-02 13:19 ` William Dauchy
2015-07-08 7:28 ` Greg KH
2015-07-09 13:42 ` Luis Henriques
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=20150702130719.GA5256@kroah.com \
--to=greg@kroah.com \
--cc=david.e.box@linux.intel.com \
--cc=hpa@linux.intel.com \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=william@gandi.net \
/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;
as well as URLs for NNTP newsgroup(s).