From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the tip tree with the kgdb tree
Date: Mon, 01 Feb 2010 09:46:26 -0600 [thread overview]
Message-ID: <4B66F752.1070001@windriver.com> (raw)
In-Reply-To: <20100201172952.95fe2150.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in
> arch/x86/kernel/kgdb.c between commit
> 53a2aa296b5108e9bfdcda7f41221e721d9c7474 ("x86,hw_breakpoint,kgdb: kgdb
> to use hw_breakpoint API") from the kgdb tree and commit
> cc0967490c1c3824bc5b75718b6ca8a51d9f2617 ("x86, hw_breakpoints, kgdb: Fix
> kgdb to use hw_breakpoint API") from the tip tree.
>
> These two commits are similar but sufficiently different to make a mess.
> I effectively reverted the kgdb tree version and used the tip tree
> version. This also involved reverting the kgdb tree changes to
> arch/x86/kernel/hw_breakpoint.c. I hope I got it right (since I had to
> reapply a few other kgdb changes by hand) (an x86_64 allmodconfig build
> produces no new warnings or errors, so I have some hope).
>
> Someone should give me some guidance as to a way forward here, please.
>
>
What is in tip is the correct version.
It is the age old time dependency of who updates whose tree first, vs
when the linux-next merge runs. At any rate this is already resolved.
Thanks,
Jason.
next prev parent reply other threads:[~2010-02-01 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 6:29 linux-next: manual merge of the tip tree with the kgdb tree Stephen Rothwell
2010-02-01 15:46 ` Jason Wessel [this message]
2010-02-01 23:25 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-05-14 4:14 Stephen Rothwell
2010-05-14 14:00 ` Don Zickus
2010-01-14 5:13 Stephen Rothwell
2010-01-14 9:26 ` Ingo Molnar
2010-01-14 15:01 ` Jason Wessel
2010-01-14 15:20 ` Steven Rostedt
2010-01-14 15:49 ` Jason Wessel
2009-10-28 7:04 Stephen Rothwell
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=4B66F752.1070001@windriver.com \
--to=jason.wessel@windriver.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.