From: Richard Weinberger <richard@nod.at>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] um: Fix a build error
Date: Mon, 15 Jun 2015 14:49:06 +0000 [thread overview]
Message-ID: <557EE5E2.7080409@nod.at> (raw)
In-Reply-To: <1434379436-8301-1-git-send-email-firogm@gmail.com>
Am 15.06.2015 um 16:43 schrieb Firo Yang:
> Gcc5 failed to build uml.
> Update codes to test __GNUC__ with 5 will be happier.
>
> Signed-off-by: Firo Yang <firogm@gmail.com>
The issue got already addressed by patches:
[PATCH 2/5] um: Stop abusing __KERNEL__
[PATCH 3/5] um: Remove copy&paste code from init.h
They will appear soon in Linus' tree.
Thanks,
//richard
prev parent reply other threads:[~2015-06-15 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 14:43 [PATCH] um: Fix a build error Firo Yang
2015-06-15 14:49 ` Richard Weinberger [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=557EE5E2.7080409@nod.at \
--to=richard@nod.at \
--cc=kernel-janitors@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