From: "Philip Müller" <philm@manjaro.org>
To: Kamal Mostafa <kamal@canonical.com>
Cc: kernel-team@lists.ubuntu.com,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [3.19.y-ckt stable] Linux 3.19.8-ckt21
Date: Mon, 16 May 2016 19:38:41 +0200 [thread overview]
Message-ID: <16093de2-8619-834b-32e4-c27870ece4d6@manjaro.org> (raw)
In-Reply-To: <20160516165809.GA12356@whence.com>
On 16.05.2016 18:58, Kamal Mostafa wrote:
>
> Queued up for 3.19-stable. Thanks very much for the backport, Philip.
>
> -Kamal
>
Thx. Due this fact I also found another issue with it. Somehow some
other patch is needed to get it compiled with gcc 6.1 series.
https://github.com/manjaro/packages-core/issues/40
It simply fails with:
In file included from drivers/hid/hid-hyperv.c:16:0:
include/linux/module.h:138:40: error: storage size of
‘__mod_vmbus__id_table_device_table’ isn’t known
extern const struct type##_device_id
__mod_##type##__##name##_device_table \
^
drivers/hid/hid-hyperv.c:594:1: note: in expansion of macro
‘MODULE_DEVICE_TABLE’
MODULE_DEVICE_TABLE(vmbus, id_table);
^~~~~~~~~~~~~~~~~~~
scripts/Makefile.build:263: recipe for target 'drivers/hid/hid-hyperv.o'
failed
make[2]: *** [drivers/hid/hid-hyperv.o] Error 1
scripts/Makefile.build:402: recipe for target 'drivers/hid' failed
make[1]: *** [drivers/hid] Error 2
make[1]: *** Waiting for unfinished jobs....
This happens also to 3.16.35 and 3.18.33. Any clue why? Seems gcc is a
little harsh on it.
greez
Philip Müller
-----------------------
Manjaro Project Lead
prev parent reply other threads:[~2016-05-16 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 16:06 Kamal Mostafa
2016-05-12 16:06 ` Kamal Mostafa
2016-05-12 19:07 ` Philip Müller
2016-05-12 19:56 ` Philip Müller
2016-05-16 16:58 ` Kamal Mostafa
2016-05-16 17:38 ` Philip Müller [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=16093de2-8619-834b-32e4-c27870ece4d6@manjaro.org \
--to=philm@manjaro.org \
--cc=kamal@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®