On 24 December 2014 at 08:20, Kalle Valo <kvalo@xxxxxxxxxxxxxx> wrote: > Oscar Forner Martinez <oscar.forner.martinez@xxxxxxxxx> writes: > >> Three lines with more than 80 characters per line have been split in several lines. >> >> Signed-off-by: Oscar Forner Martinez <oscar.forner.martinez@xxxxxxxxx> >> --- >> drivers/bcma/driver_chipcommon.c | 10 +++++++--- >> 1 file changed, 7 insertions(+), 3 deletions(-) > > Just to handle the bureaucracy before v2 is submitted: > > To which tree should this go to? I see that earlier John has applied > patches to drivers/bcma/, but what about now? Should I take these? John, > any suggestions? bcma is a bus with multiple cores (devices) As some of cores (devices) are very simply to handle and/or they are needed very early (e.g. for initialization), bcma has: 1) Few bult-in drivers (like MIPS, ChipCommon) 2) Few "external" drivers using standard bus mechanism (e.g. b43, brcmsmac, bgmac) I guess the biggest bcma users are wireless drivers, so bcma was also maintained using wireless tree. Unfortunately bus can't be just setup once and not touched anymore. Drivers often need to touch ChipCommon so there are some export_symbol-s in driver_chipcommon.c and you also can get patchset-s touching bcma and then wireless driver. Of course there are some problems with such maintenance. Rarely I've to do changes in arch/mips/bcm47xx/ code, wait for a release and then change sth in drivers/bcma. But I don't see a better solution for all of this. -- Rafał -- 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
