From: Jason Wessel <jason.wessel@windriver.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kgdb-bugreport@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
jbarnes@virtuousgeek.org, linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for December 31 (kgdb)
Date: Fri, 01 Jan 2010 23:33:08 -0600 [thread overview]
Message-ID: <4B3EDA94.3040005@windriver.com> (raw)
In-Reply-To: <12c511ca0912311120i3f60fccas3487c1f47b5cf3c3@mail.gmail.com>
Tony Luck wrote:
> The kgdb bits break ia64 (and any other architecture without an
> <asm/kgdb.h> too):
>
>
Certainly this was not intended. It is properly fixed now in and
folded into a number of the kgdb patches so everything will properly
bisect. It is updated in kgdb-next.
Thanks,
Jason.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
next prev parent reply other threads:[~2010-01-02 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 0:23 linux-next: Tree for December 31 Stephen Rothwell
2009-12-31 19:07 ` linux-next: Tree for December 31 (kgdb) Randy Dunlap
2009-12-31 19:20 ` Tony Luck
2010-01-01 1:04 ` Stephen Rothwell
2010-01-01 21:18 ` Tony Luck
2010-01-02 5:33 ` Jason Wessel [this message]
2010-01-02 11:32 ` Stephen Rothwell
2010-01-02 5:35 ` Jason Wessel
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=4B3EDA94.3040005@windriver.com \
--to=jason.wessel@windriver.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).