mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Philip Müller" <philm@manjaro.org>
To: Willy Tarreau <w@1wt.eu>
Cc: ben@decadent.org.uk,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [linux310][linux316] Backport of 'compiler-gcc: integrate the various compiler-gcc[345].h'
Date: Wed, 18 May 2016 19:07:03 +0200	[thread overview]
Message-ID: <0d11377d-0c02-84f1-e884-72b8e34dea14@manjaro.org> (raw)
In-Reply-To: <20160518143802.GH14904@1wt.eu>

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

Am 18.05.2016 um 16:38 schrieb Willy Tarreau:
> Hi Philip,
> Now queued for 3.10, thanks!
> willy
> 

Hi Willy,

you need that snippet also to make it work. Backport of commit
c4586256f0c440bc2bdb29d2cbb915f0ca785d26 upstream.
Similar to the fix in 40413dcb7b273bda681dca38e6ff0bbb3728ef11

Here is Greg's version:
https://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/tree/releases/3.14.69/x86-llvmlinux-fix-incomplete-type-const-struct-x86cpu_device_id.patch

signed-by philm@manjaro.org

greez
Philip




[-- Attachment #2: fix-mod_devicetable.patch --]
[-- Type: text/x-patch, Size: 1043 bytes --]

diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index 45e9214..740c6df 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -398,6 +398,7 @@ struct virtio_device_id {
 /*
  * For Hyper-V devices we use the device guid as the id.
  */
+#define vmbus_device_id hv_vmbus_device_id
 struct hv_vmbus_device_id {
 	__u8 guid[16];
 	kernel_ulong_t driver_data;	/* Data private to the driver */
@@ -548,6 +549,11 @@ struct amba_id {
  * See documentation of "x86_match_cpu" for details.
  */
 
+/*
+ * MODULE_DEVICE_TABLE expects this struct to be called x86cpu_device_id.
+ * Although gcc seems to ignore this error, clang fails without this define.
+ */
+#define x86cpu_device_id x86_cpu_id
 struct x86_cpu_id {
 	__u16 vendor;
 	__u16 family;
@@ -575,6 +581,7 @@ struct ipack_device_id {
 #define MEI_CL_MODULE_PREFIX "mei:"
 #define MEI_CL_NAME_SIZE 32
 
+#define mei_device_id mei_cl_device_id
 struct mei_cl_device_id {
 	char name[MEI_CL_NAME_SIZE];
 	kernel_ulong_t driver_info;

  reply	other threads:[~2016-05-18 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 14:38 Philip Müller
2016-05-17 15:11 ` Philip Müller
2016-06-04 16:34   ` Ben Hutchings
2016-05-18 14:38 ` Willy Tarreau
2016-05-18 17:07   ` Philip Müller [this message]
2016-05-18 17:34     ` Willy Tarreau

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=0d11377d-0c02-84f1-e884-72b8e34dea14@manjaro.org \
    --to=philm@manjaro.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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®