From: "Peter Teoh" <htmldeveloper@gmail.com>
To: linux-mm@kvack.org,
"kernelnewbies@nl.linux.org" <kernelnewbies@nl.linux.org>
Subject: Re: git-pull conflict - how to solve it?
Date: Tue, 5 Feb 2008 18:16:54 +0800 [thread overview]
Message-ID: <804dabb00802050216y50d1dfcasf8d5cdcf466ea58d@mail.gmail.com> (raw)
In-Reply-To: <804dabb00802050148l3b379016we5fc54f326121276@mail.gmail.com>
I suspect the git source is having some problem. Because after I
deleted the file, did a git checkout -f again, the ioremap.c comes
back with the corrupted contents.
--- ioremap.c 2008-02-05 11:01:45.000000000 +0800
+++ /tmp/ioremap.c 2008-02-05 17:37:12.000000000 +0800
@@ -103,6 +103,10 @@ static void __iomem *__ioremap(unsigned
{
unsigned long pfn, offset, last_addr, vaddr;
struct vm_struct *area;
+<<<<<<< HEAD:arch/x86/mm/ioremap.c
+ unsigned long pfn, offset, last_addr;
+=======
+>>>>>>> 5329cf8e19bd83f8d9e0b6b2a3cdcfbd288eb68e:arch/x86/mm/ioremap.c
pgprot_t prot;
/* Don't allow wraparound or zero size */
@@ -121,8 +125,12 @@ static void __iomem *__ioremap(unsigned
*/
for (pfn = phys_addr >> PAGE_SHIFT; pfn < max_pfn_mapped &&
(pfn << PAGE_SHIFT) < last_addr; pfn++) {
+<<<<<<< HEAD:arch/x86/mm/ioremap.c
+ if (pfn_valid(pfn) && !PageReserved(pfn_to_page(pfn)))
+=======
if (page_is_ram(pfn) && pfn_valid(pfn) &&
!PageReserved(pfn_to_page(pfn)))
+>>>>>>> 5329cf8e19bd83f8d9e0b6b2a3cdcfbd288eb68e:arch/x86/mm/ioremap.c
return NULL;
}
where is diff is wrt to linus-tree.
Therefore, I copied over the ioremap.c from linus tree and continued
my compilation.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-05 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 9:48 Peter Teoh
2008-02-05 10:15 ` Robert P. J. Day
2008-02-05 10:16 ` Peter Teoh [this message]
2008-02-05 10:23 ` Robert P. J. Day
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=804dabb00802050216y50d1dfcasf8d5cdcf466ea58d@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-mm@kvack.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