Re: [RFC][PATCH] axi: add AXI bus driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/4/12 RafaÅ MiÅecki <zajec5@xxxxxxxxx>:
> Cc: Michael BÃsch <mb@xxxxxxxxx>
> Cc: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
> Cc: George Kashperko <george@xxxxxxxxxxx>
> Cc: Arend van Spriel <arend@xxxxxxxxxxxx>
> Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> Cc: Russell King <rmk@xxxxxxxxxxxxxxxx>
> Cc: Arnd Bergmann <arnd@xxxxxxxx>
> Cc: Andy Botting <andy@xxxxxxxxxxxxxxx>
> Cc: linuxdriverproject <devel@xxxxxxxxxxxxxxxxxxxxxx>
> Cc: linux-kernel@xxxxxxxxxxxxxxx <linux-kernel@xxxxxxxxxxxxxxx>
> Signed-off-by: RafaÅ MiÅecki <zajec5@xxxxxxxxx>
> ---
> V2: Rename to axi
> Â ÂUse DEFINE_PCI_DEVICE_TABLE in bridge
> Â ÂMake use of pr_fmt and pr_*
> Â ÂStore core class
> Â ÂRename bridge to not b43 specific
> Â ÂReplace magic 0x1000 with BCMAI_CORE_SIZE
> Â ÂRemove some old "ssb" names and defines
> Â ÂMove BCMAI_ADDR_BASE def
> Â ÂAdd drvdata field
> V3: Fix reloading (kfree issue)
> Â ÂAdd 14e4:0x4331
> Â ÂFix non-initialized struct issue
> Â ÂDrop useless inline functions wrappers for pci core drv
> Â ÂProper pr_* usage
> V3.1: Include forgotten changes (pr_* and include related)
> Â ÂExplain why we dare to implement empty release function

There is one more change I started to consider. Is "core" correct name
for AXI's device? Almost everywhere we can read about *components* on
the AXI interconnect.

Maybe it'd make sense to s/core/comp/? Arend?

-- 
RafaÅ
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel



[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux