From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Michael Matz <matz@suse.de>,
linux-kernel@vger.kernel.org, x86-ml <x86@kernel.org>
Subject: Re: X86 GIT GCC 5 compilation warning
Date: Tue, 16 Jun 2015 16:42:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.20.1506161641270.432@localhost.localdomain> (raw)
In-Reply-To: <20150616135801.GH17786@pd.tnic>
Hi guys.
I am running the new kernel - and all is well.
Thank you.
Enrico Mioso
next prev parent reply other threads:[~2015-06-16 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 15:14 X86 GIT GCC 5 compilation warning Enrico Mioso
2015-06-14 18:07 ` Borislav Petkov
2015-06-15 11:30 ` Michael Matz
2015-06-15 17:17 ` Borislav Petkov
2015-06-16 11:59 ` Michael Matz
2015-06-16 12:39 ` Enrico Mioso
2015-06-16 12:47 ` Michael Matz
2015-06-16 13:58 ` Borislav Petkov
2015-06-16 14:09 ` Enrico Mioso
2015-06-16 14:42 ` Enrico Mioso [this message]
2015-06-16 15:32 ` Borislav Petkov
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=alpine.LNX.2.20.1506161641270.432@localhost.localdomain \
--to=mrkiko.rs@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matz@suse.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).