> Hi, > Thanks for the patch, but I still get these errors & warnings: > > on linux-next 2010-0915: > > drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c: In function > 'SetupHIFScatterSupport': > drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:288: error: > 'struct mmc_host' has no member named 'max_hw_segs' > drivers/staging/ath6kl/hif/sdio/linux_sdio/src/hif_scatter.c:289: error: > 'struct mmc_host' has no member named 'max_hw_segs' > This is because of a recent change in the mmc_host structure that removes the distinction between hw and phys segments. The structure is different in the staging-next-2.6 tree which is where I usually build and test the changes. Greg, The two trees linux-next and staging-next are not in sync so what is the process that is usually followed under these circumstances? I see little point in using the staging-next-2.6 tree to generate and test my patches since the tree eventually drains into linux-next. Should I stop worrying about if the patch works for the staging-next tree and just focus on that things should work with linux-next? > and on linux-next 2010-0917: > > drivers/staging/ath6kl/os/linux/ar6000_drv.c: In function > 'ar6000_transfer_bin_file': > drivers/staging/ath6kl/os/linux/ar6000_drv.c:1129: warning: cast from > pointer to integer of different size > drivers/staging/ath6kl/os/linux/ar6000_drv.c:1129: warning: cast to > pointer from integer of different size > drivers/staging/ath6kl/wmi/wmi.c: In function 'wmi_bssInfo_event_rx': > drivers/staging/ath6kl/wmi/wmi.c:1459: error: 'i' undeclared (first use in > this function) > > This is due to a recent patch that went it to use '%pM' format specifier to print MAC addresses. I'll fix it. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
