From: David Witbrodt <dawitbro@sbcglobal.net>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late v2
Date: Fri, 29 Aug 2008 12:00:45 -0700 (PDT) [thread overview]
Message-ID: <779431.38300.qm@web82104.mail.mud.yahoo.com> (raw)
> can you check tip/master now? Ingo fixed it arlready...
Yinghai,
Before updating my git tree, I copied some files (in their
respective directories):
e820.c ==> e820.c.yh
i386.c ==> i386.c.yh
e820.h ==> e820.h.yh
Then I updated and checked out tip/master:
git remote update
git checkout -f tip/master
Running diffs on the updated files and the old files with your
patches (i.e., 'diff e820.c{,.yh}') confirmed that the files
were the same.
However, for the sake of paranoia prevention, I went ahead and
built the kernel and rebooted: it worked perfectly.
Thx,
Dave W.
next reply other threads:[~2008-08-29 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 19:00 David Witbrodt [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-31 19:10 [PATCH] x86: split e820 reserved entries record to late v2 David Witbrodt
2008-08-29 14:48 David Witbrodt
2008-08-29 17:46 ` Yinghai Lu
2008-08-29 14:32 David Witbrodt
2008-08-31 17:18 ` Francois Romieu
2008-08-29 3:59 David Witbrodt
2008-08-29 5:06 ` Yinghai Lu
2008-08-28 20:34 Yinghai Lu
2008-08-28 20:40 ` Linus Torvalds
2008-08-28 20:52 ` Yinghai Lu
2008-08-28 20:58 ` Ingo Molnar
2008-08-28 21:16 ` Ingo Molnar
2008-08-29 0:21 ` H. Peter Anvin
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=779431.38300.qm@web82104.mail.mud.yahoo.com \
--to=dawitbro@sbcglobal.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel@gmail.com \
/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