Hi Andy,
On Tue, 15 Oct 2019 11:04:29 +0300 Andy Shevchenko
wrote:
>
> Oops, thank you for pointing out, should be fixed.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
pgpBwIoBHkfdq.pgp
Description: OpenPGP digital signature
On Tue, Oct 15, 2019 at 5:00 AM Stephen Rothwell wrote:
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/platform/x86/huawei-wmi.c: In function 'huawei_wmi_exit':
> drivers/platform/x86/huawei-wmi.c:890:41: error: 'struct
Hi all,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/huawei-wmi.c: In function 'huawei_wmi_exit':
drivers/platform/x86/huawei-wmi.c:890:41: error: 'struct huawei_wmi' has no
member named 'pdev'; did you mean 'idev'?
On June 11, 2018 6:23:10 PM PDT, Stephen Rothwell wrote:
>Hi all,
>
>After merging the drivers-x86 tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>
>drivers/platform/x86/silead_dmi.c:84:21: error: variable
>'chuwi_vi10_data' has initializer but incomplete type
> static
On June 11, 2018 6:23:10 PM PDT, Stephen Rothwell wrote:
>Hi all,
>
>After merging the drivers-x86 tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>
>drivers/platform/x86/silead_dmi.c:84:21: error: variable
>'chuwi_vi10_data' has initializer but incomplete type
> static
On Tue, Jun 12, 2018 at 11:23:10AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/platform/x86/silead_dmi.c:84:21: error: variable 'chuwi_vi10_data'
> has initializer but incomplete
On Tue, Jun 12, 2018 at 11:23:10AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/platform/x86/silead_dmi.c:84:21: error: variable 'chuwi_vi10_data'
> has initializer but incomplete
Hi all,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/silead_dmi.c:84:21: error: variable 'chuwi_vi10_data' has
initializer but incomplete type
static const struct ts_dmi_data chuwi_vi10_data = {
Hi all,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/silead_dmi.c:84:21: error: variable 'chuwi_vi10_data' has
initializer but incomplete type
static const struct ts_dmi_data chuwi_vi10_data = {
On Fri, Jun 05, 2015 at 08:13:01PM +1000, Michael Ellerman wrote:
> Hi Darren,
>
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig)
> failed like this:
>
> ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko]
> undefined!
>
> Caused by
On Thu, Jun 04, 2015 at 07:51:36PM +0200, Radim Krčmář wrote:
> 2015-06-04 18:13+1000, Stephen Rothwell:
> > After merging the drivers-x86 tree, today's linux-next build (x86_64
> > allmodconfig)
> > failed like this:
> >
> > ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko]
On Thu, Jun 04, 2015 at 07:51:36PM +0200, Radim Krčmář wrote:
2015-06-04 18:13+1000, Stephen Rothwell:
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: acpi_bus_get_status_handle [drivers/platform/x86/pvpanic.ko]
undefined!
On Fri, Jun 05, 2015 at 08:13:01PM +1000, Michael Ellerman wrote:
Hi Darren,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: acpi_bus_get_status_handle [drivers/platform/x86/pvpanic.ko]
undefined!
Caused by commit
Hi Darren,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko] undefined!
Caused by commit b8f8cf6b02b6 ("pvpanic: handle missing _STA correctly").
I have applied the fixup
Hi Darren,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: acpi_bus_get_status_handle [drivers/platform/x86/pvpanic.ko] undefined!
Caused by commit b8f8cf6b02b6 (pvpanic: handle missing _STA correctly).
I have applied the fixup patch
2015-06-04 18:13+1000, Stephen Rothwell:
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig)
> failed like this:
>
> ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko]
> undefined!
>
> Caused by commit b8f8cf6b02b6 ("pvpanic: handle missing
Hi Darren,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: "acpi_bus_get_status_handle" [drivers/platform/x86/pvpanic.ko] undefined!
Caused by commit b8f8cf6b02b6 ("pvpanic: handle missing _STA correctly").
I have used the
2015-06-04 18:13+1000, Stephen Rothwell:
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: acpi_bus_get_status_handle [drivers/platform/x86/pvpanic.ko]
undefined!
Caused by commit b8f8cf6b02b6 (pvpanic: handle missing _STA
Hi Darren,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig)
failed like this:
ERROR: acpi_bus_get_status_handle [drivers/platform/x86/pvpanic.ko] undefined!
Caused by commit b8f8cf6b02b6 (pvpanic: handle missing _STA correctly).
I have used the drivers-x86
Hi,
The commit 154a7a7b2234 ("asus-wmi: update wlan LED through rfkill led trigger")
needs another patch which was submitted to rfkill, but still not be merged yet.
see https://patchwork.kernel.org/patch/1240091/
Sorry for leading to the problem.
Best regards,
AceLan Kao.
2012/8/20 Stephen
Hi Matthew,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/asus-wmi.c: In function 'asus_new_rfkill':
drivers/platform/x86/asus-wmi.c:892:3: error: implicit declaration of function
'rfkill_set_led_trigger_name'
Hi Matthew,
After merging the drivers-x86 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/platform/x86/asus-wmi.c: In function 'asus_new_rfkill':
drivers/platform/x86/asus-wmi.c:892:3: error: implicit declaration of function
'rfkill_set_led_trigger_name'
Hi,
The commit 154a7a7b2234 (asus-wmi: update wlan LED through rfkill led trigger)
needs another patch which was submitted to rfkill, but still not be merged yet.
see https://patchwork.kernel.org/patch/1240091/
Sorry for leading to the problem.
Best regards,
AceLan Kao.
2012/8/20 Stephen
23 matches
Mail list logo