Messages in this thread | | | Date | Fri, 24 Jun 2005 14:39:15 +0200 | From | Petr Baudis <> | Subject | Re: Finding what change broke ARM |
| |
Dear diary, on Fri, Jun 24, 2005 at 11:19:51AM CEST, I got a letter where Russell King <rmk+lkml@arm.linux.org.uk> told me that... > When building current git for ARM, I see: > > CC arch/arm/mm/consistent.o > arch/arm/mm/consistent.c: In function `dma_free_coherent': > arch/arm/mm/consistent.c:357: error: `mem_map' undeclared (first use in this function) > arch/arm/mm/consistent.c:357: error: (Each undeclared identifier is reported only once > arch/arm/mm/consistent.c:357: error: for each function it appears in.) > make[2]: *** [arch/arm/mm/consistent.o] Error 1 > > How can I find what change elsewhere in the kernel tree caused this > breakage? > > With bk, you could ask for a per-file revision history of the likely > candidates, and then find the changeset to view the other related > changes. > > With git... ? We don't have per-file revision history so...
With Cogito, you can pass cg-log list of files, and it will show only the history of the given files.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ <Espy> be careful, some twit might quote you out of context.. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |