git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Finding what change broke ARM

From
RKRussell King <rmk+lkml@arm.linux.org.uk>
Date
Jun 24, 2005, 09:19 UTC
Message-ID
<20050624101951.B23185@flint.arm.linux.org.uk>
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...
-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
Next: Alecs King
Message 1 of 4 in “Finding what change broke ARM”
  1. Russell KingJun 24, 2005
  2. Alecs KingJun 24, 2005
  3. Petr BaudisJun 24, 2005
  4. Linus TorvaldsJun 24, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.