From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (kgdb tree related)
Date: Mon, 1 Aug 2011 07:42:59 -0500 [thread overview]
Message-ID: <4E369F53.4040903@windriver.com> (raw)
In-Reply-To: <20110801142257.0fe7bcceaa0c61527b9597c3@canb.auug.org.au>
On 07/31/2011 11:22 PM, Stephen Rothwell wrote:
> Hi Jason,
>
> After merging the final tree, today's linux-next build (sparc32_defconfig)
> failed like this:
>
> kernel/debug/gdbstub.c: In function 'gdbstub_state':
> kernel/debug/gdbstub.c:1098:3: error: 'gdbstub_use_prev_in_buf' undeclared (first use in this function)
> kernel/debug/gdbstub.c:1098:3: note: each undeclared identifier is reported only once for each function it appears in
> kernel/debug/gdbstub.c:1099:3: error: 'gdbstub_prev_in_buf_pos' undeclared (first use in this function)
>
> Caused by commit faed702e3b31 ("kdb,kgdb: Implement switch and pass
> buffer from kdb -> gdb").
>
> I reverted that commit (and 621ebf205b99 "kdb: Remove all references to
> DOING_KGDB2" and "kdb,kgdb: Allow arbitrary kgdb magic knock
> sequences" that depend on it) for today.
>
> BTW, that last commit (29e3c61ef33c) doesn't have a SOB line.
Thanks for the detailed report. I fixed this by re-basing kgdb-next against the kgdb-dev branch. These branches are not supposed to get out of sync. I'll try and figure out what went wrong. :-)
Jason.
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (kgdb tree related)
Date: Mon, 1 Aug 2011 07:42:59 -0500 [thread overview]
Message-ID: <4E369F53.4040903@windriver.com> (raw)
In-Reply-To: <20110801142257.0fe7bcceaa0c61527b9597c3@canb.auug.org.au>
On 07/31/2011 11:22 PM, Stephen Rothwell wrote:
> Hi Jason,
>
> After merging the final tree, today's linux-next build (sparc32_defconfig)
> failed like this:
>
> kernel/debug/gdbstub.c: In function 'gdbstub_state':
> kernel/debug/gdbstub.c:1098:3: error: 'gdbstub_use_prev_in_buf' undeclared (first use in this function)
> kernel/debug/gdbstub.c:1098:3: note: each undeclared identifier is reported only once for each function it appears in
> kernel/debug/gdbstub.c:1099:3: error: 'gdbstub_prev_in_buf_pos' undeclared (first use in this function)
>
> Caused by commit faed702e3b31 ("kdb,kgdb: Implement switch and pass
> buffer from kdb -> gdb").
>
> I reverted that commit (and 621ebf205b99 "kdb: Remove all references to
> DOING_KGDB2" and "kdb,kgdb: Allow arbitrary kgdb magic knock
> sequences" that depend on it) for today.
>
> BTW, that last commit (29e3c61ef33c) doesn't have a SOB line.
Thanks for the detailed report. I fixed this by re-basing kgdb-next against the kgdb-dev branch. These branches are not supposed to get out of sync. I'll try and figure out what went wrong. :-)
Jason.
next prev parent reply other threads:[~2011-08-01 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 4:22 linux-next: build failure after merge of the final tree (kgdb tree related) Stephen Rothwell
2011-08-01 12:42 ` Jason Wessel [this message]
2011-08-01 12:42 ` Jason Wessel
-- strict thread matches above, loose matches on Subject: below --
2010-07-28 4:05 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=4E369F53.4040903@windriver.com \
--to=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.