From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vincent <vincent.stehle@laposte.net>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH] topology: Fix compilation warning when not in SMP
Date: Sat, 5 Apr 2014 10:20:00 -0700 [thread overview]
Message-ID: <20140405172000.GB3850@kroah.com> (raw)
In-Reply-To: <533FF763.3020000@bergerie>
On Sat, Apr 05, 2014 at 02:30:27PM +0200, Vincent wrote:
> On 04/05/2014 01:49 AM, Greg Kroah-Hartman wrote:
> > Warnings aren't a stable kernel issue, so why would this be relevant
> > there?
>
> Oh, sorry about that. I'll go re-read the stable kernel rules again.
>
> Shall I re-post without the stable Cc:, for only mainline and next?
No need, I'll just remove them when I apply the patch.
thanks,
greg k-h
prev parent reply other threads:[~2014-04-05 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 6:43 [PATCH] topology: Fix compilation warning when not in SMP Vincent Stehlé
2014-04-04 23:49 ` Greg Kroah-Hartman
2014-04-05 12:30 ` Vincent
2014-04-05 17:20 ` Greg Kroah-Hartman [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=20140405172000.GB3850@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vincent.stehle@laposte.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