diff options
| author | Ingo Molnar <mingo@elte.hu> | 2008-05-05 01:06:54 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2008-05-05 01:06:54 -0700 |
| commit | 7a1aa309f21ea2f6c31f364341e4027ecf4e79bc (patch) | |
| tree | d93a1ce044477aefb464ce92512fd4025b535228 /net/dccp/feat.c | |
| parent | c17f888f8fc2e47e2b4a51424f8ccf564ae87576 (diff) | |
| download | kernel_samsung_smdk4412-7a1aa309f21ea2f6c31f364341e4027ecf4e79bc.zip kernel_samsung_smdk4412-7a1aa309f21ea2f6c31f364341e4027ecf4e79bc.tar.gz kernel_samsung_smdk4412-7a1aa309f21ea2f6c31f364341e4027ecf4e79bc.tar.bz2 | |
irda: fix !PNP support for drivers/net/irda/smsc-ircc2.c
x86.git testing found this build bug on v2.6.26-rc1:
ERROR: "pnp_get_resource" [drivers/net/irda/smsc-ircc2.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
the driver did not anticipate the case of !CONFIG_PNP which is rare but
still possible. Instead of restricting the driver to PNP-only in the
Kconfig space, add the (trivial) dummy struct pnp_driver - this is that
other drivers use in the !PNP case too.
The driver itself can in theory be initialized on !PNP too in certain
cases, via smsc_ircc_legacy_probe().
Patch only minimally build tested, i dont have this hardware.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dccp/feat.c')
0 files changed, 0 insertions, 0 deletions