On Tue, Mar 13, 2012 at 6:39 PM, Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx> wrote: > Hi guys, > > I've not bisected to concretely determine this is true, but at 1st > glance, it would appear perhaps that the change: > > ------------- > commit f1e1e148c5cbf62b6db26ae828c1e54e76579dfd > Author: Michael Walle <michael@xxxxxxxx> > Date: Sun Nov 13 22:23:57 2011 +0100 > > ARM: kirkwood: sata_mv: add device tree binding > > Based on devicetree work by Michael Walle. Changed compatible property > to "mrvl,orion-sata", simplified retrieving nr_ports from fdt. > > Signed-off-by: Michael Walle <michael@xxxxxxxx> > Signed-off-by: Jason Cooper <jason@xxxxxxxxxxxxxx> > -------------- > > might be responsible for these new sparc build failures? > > http://kisskb.ellerman.id.au/kisskb/buildresult/5869562/ > http://kisskb.ellerman.id.au/kisskb/buildresult/5869535/ > > If you could confirm or deny, that would be great help. Just a follow up to this -- I just realized that the linux-next toolchain for sparc changed, so that *may* somehow have a bearing on this (i.e. how weak is handled etc etc.) P. -- > > Thanks, > Paul. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
