These four patches fix build issues reported by Randy Dunlap on the
linux-next tree for Jan 6 and Jan 7:
http://lkml.org/lkml/2009/1/6/340http://lkml.org/lkml/2009/1/7/360
The issue fixed by patch #3 wasn't reported on the emails but was
uncovered while discussing the fixes.
This applies to the wimax tree kept in gregkh's repository:
http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-04-usb/
Changes in v3
- Add patch #4, wrapping access to power-saving members of the struct
usb_device in #ifdef CONFIG_PM.
Changes in v2
- fixed silly one-char typo #ifndef CONFIG_BUG vs #ifdef CONFIG_BUG
reported by Ilpo J��rvinen
Inaky Perez-Gonzalez (4):
wimax: fix '#ifndef CONFIG_BUG' layout to avoid warning
wimax: fix kconfig interactions with rfkill and input layers
wimax: testing for rfkill support should also test for
CONFIG_RFKILL_MODULE
i2400m/usb: wrap USB power saving in #ifdef CONFIG_PM
drivers/net/wimax/i2400m/usb.c | 6 ++++++
net/wimax/Kconfig | 14 ++++++++++++++
net/wimax/id-table.c | 8 +++++---
net/wimax/op-rfkill.c | 2 +-
4 files changed, 26 insertions(+), 4 deletions(-)
Also, this warning needs to be fixed:
linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90
forbids mixed declarations and code
Move the return on #defined(CONFIG_BUG) below the variable
declarations so it doesn't violate ISO C90.
On wimax_id_table_release() we want to do a debug check if CONFIG_BUG
is enabled. However, we also want the debug code to be always compiled
to ensure there is no bitrot. It will be optimized out by the compiler
when CONFIG_BUG is disabled.
Added a note to the function header stating this.
Signed-off-by: Inaky Perez-Gonzalez <redacted>
---
net/wimax/id-table.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
WiMAX can work without RFKILL, but it was missing a check to make sure
RFKILL is not being made a module with wimax compiled into the
kernel. This caused failed builds in s390, where CONFIG_INPUT is
always off.
When RFKILL is enabled, the code uses the input layer to report
hardware switch changes; thus, if RFKILL is enabled, INPUT has to be
too. It also needs to display some message when INPUT is disabled that
explains why WiMAX is not selectable.
(issues found by Randy Dunlap in the linux-next tree).
Signed-off-by: Inaky Perez-Gonzalez <redacted>
---
net/wimax/Kconfig | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
@@ -1,9 +1,23 @@## WiMAX LAN device configuration#+# Note the ugly 'depends on' on WIMAX: that disallows RFKILL to be a+# module if WIMAX is to be linked in. The WiMAX code is done in such a+# way that it doesn't require and explicit dependency on RFKILL in+# case an embedded system wants to rip it out.+#+# As well, enablement of the RFKILL code means we need the INPUT layer+# support to inject events coming from hw rfkill switches. That+# dependency could be killed if input.h provided appropiate means to+# work when input is disabled.++comment"WiMAX Wireless Broadband support requires CONFIG_INPUT enabled"+depends onINPUT=n&&RFKILL!=nmenuconfigWIMAXtristate"WiMAX Wireless Broadband support"+depends on(y&&RFKILL!=m)||m+depends on(INPUT&&RFKILL!=n)||RFKILL=nhelpSelecttoconfiguresupportfordevicesthatprovide
Current code was assuming PM was always enabled, which is not
correct. Code which accesses members in the struct usb_device that are
dependant on CONFIG_PM must be protected the same.
Reported by Randy Dunlap from a build error in the linux-next tree on
07/01/2009.
Signed-off-by: Inaky Perez-Gonzalez <redacted>
Cc: Randy Dunlap <redacted>
---
drivers/net/wimax/i2400m/usb.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
@@ -503,11 +507,13 @@ int i2400mu_suspend(struct usb_interface *iface, pm_message_t pm_msg)atomic_dec(&i2400mu->do_autopm);result=i2400m_cmd_enter_powersave(i2400m);atomic_inc(&i2400mu->do_autopm);+#ifdef CONFIG_PMif(result<0&&usb_dev->auto_pm==0){/* System suspend, can't fail */dev_err(dev,"failed to suspend, will reset on resume\n");result=0;}+#endifif(result<0)gotoerror_enter_powersave;i2400mu_notification_release(i2400mu);
Current WiMAX rfkill code is missing the case where rfkill is compiled
in as modules and works only when rfkill is compiled in. This is not
correct. Fixed to test for CONFIG_RFKILL or CONFIG_RKILL_MODULE.
Signed-off-by: Inaky Perez-Gonzalez <redacted>
---
net/wimax/op-rfkill.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Changes in v3
- Add patch #4, wrapping access to power-saving members of the struct
usb_device in #ifdef CONFIG_PM.
Changes in v2
- fixed silly one-char typo #ifndef CONFIG_BUG vs #ifdef CONFIG_BUG
reported by Ilpo Järvinen
Inaky Perez-Gonzalez (4):
wimax: fix '#ifndef CONFIG_BUG' layout to avoid warning
wimax: fix kconfig interactions with rfkill and input layers
wimax: testing for rfkill support should also test for
CONFIG_RFKILL_MODULE
i2400m/usb: wrap USB power saving in #ifdef CONFIG_PM
drivers/net/wimax/i2400m/usb.c | 6 ++++++
net/wimax/Kconfig | 14 ++++++++++++++
net/wimax/id-table.c | 8 +++++---
net/wimax/op-rfkill.c | 2 +-
4 files changed, 26 insertions(+), 4 deletions(-)
Also, this warning needs to be fixed:
linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90
forbids mixed declarations and code
Move the return on #defined(CONFIG_BUG) below the variable
declarations so it doesn't violate ISO C90.
On wimax_id_table_release() we want to do a debug check if CONFIG_BUG
is enabled. However, we also want the debug code to be always compiled
to ensure there is no bitrot. It will be optimized out by the compiler
when CONFIG_BUG is disabled.
Added a note to the function header stating this.
Signed-off-by: Inaky Perez-Gonzalez <redacted>
WiMAX can work without RFKILL, but it was missing a check to make sure
RFKILL is not being made a module with wimax compiled into the
kernel. This caused failed builds in s390, where CONFIG_INPUT is
always off.
When RFKILL is enabled, the code uses the input layer to report
hardware switch changes; thus, if RFKILL is enabled, INPUT has to be
too. It also needs to display some message when INPUT is disabled that
explains why WiMAX is not selectable.
(issues found by Randy Dunlap in the linux-next tree).
Signed-off-by: Inaky Perez-Gonzalez <redacted>
Current WiMAX rfkill code is missing the case where rfkill is compiled
in as modules and works only when rfkill is compiled in. This is not
correct. Fixed to test for CONFIG_RFKILL or CONFIG_RKILL_MODULE.
Signed-off-by: Inaky Perez-Gonzalez <redacted>
Current code was assuming PM was always enabled, which is not
correct. Code which accesses members in the struct usb_device that are
dependant on CONFIG_PM must be protected the same.
Reported by Randy Dunlap from a build error in the linux-next tree on
07/01/2009.
Signed-off-by: Inaky Perez-Gonzalez <redacted>