From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Finding what change broke ARM
Date: Fri, 24 Jun 2005 10:19:51 +0100 [thread overview]
Message-ID: <20050624101951.B23185@flint.arm.linux.org.uk> (raw)
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 reply other threads:[~2005-06-24 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 9:19 Russell King [this message]
2005-06-24 11:32 ` Finding what change broke ARM Alecs King
2005-06-24 12:39 ` Petr Baudis
2005-06-24 16:03 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050624101951.B23185@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).