linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	kgdb-bugreport@lists.sourceforge.net
Subject: Re: linux-next: Tree for August 6 (kgdboc)
Date: Fri, 06 Aug 2010 15:00:57 -0500	[thread overview]
Message-ID: <4C5C69F9.5020108@windriver.com> (raw)
In-Reply-To: <20100806115344.52c712b7.randy.dunlap@oracle.com>

On 08/06/2010 01:53 PM, Randy Dunlap wrote:
> On Fri, 6 Aug 2010 13:27:58 +1000 Stephen Rothwell wrote:
> 
>> Hi all,
>>
>> As the merge window is open, please do not add 2.6.37 material to your
>> linux-next included trees until after 2.6.36-rc1.
>>
>> Changes since 20100805:
> 
> 
> ERROR: "con_debug_enter" [drivers/serial/kgdboc.ko] undefined!
> ERROR: "vc_cons" [drivers/serial/kgdboc.ko] undefined!
> ERROR: "fg_console" [drivers/serial/kgdboc.ko] undefined!
> ERROR: "con_debug_leave" [drivers/serial/kgdboc.ko] undefined!
> 
> .config is attached.
> 
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***


Any possibility you can try this patch?

I'll push it into kgdb-next in just a few min, and I created another test against this.

Thanks,
Jason.


diff --git a/include/linux/console.h b/include/linux/console.h
index f76fc29..305e9c2 100644
--- a/include/linux/console.h
+++ b/include/linux/console.h
@@ -79,8 +79,13 @@ int register_con_driver(const struct consw *csw, int first, int last);
 int unregister_con_driver(const struct consw *csw);
 int take_over_console(const struct consw *sw, int first, int last, int deflt);
 void give_up_console(const struct consw *sw);
+#ifdef CONFIG_HW_CONSOLE
 int con_debug_enter(struct vc_data *vc);
 int con_debug_leave(void);
+#else
+#define con_debug_enter()
+#define con_debug_leave()
+#endif
 
 /* scroll */
 #define SM_UP       (1)

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 

  reply	other threads:[~2010-08-06 20:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06  3:27 linux-next: Tree for August 6 Stephen Rothwell
2010-08-06 18:53 ` linux-next: Tree for August 6 (kgdboc) Randy Dunlap
2010-08-06 20:00   ` Jason Wessel [this message]
2010-08-06 21:03     ` rdunlap
2010-08-06 19:04 ` linux-next: Tree for August 6 (block git tree) Randy Dunlap
2010-08-06 19:06   ` Randy Dunlap
2010-08-10 15:37     ` Randy Dunlap
2010-08-10 15:51       ` Jens Axboe
2010-08-10 15:54         ` Randy Dunlap
2010-08-10 15:56           ` Jens Axboe
2010-08-10 15:59             ` Randy Dunlap
2010-08-10 16:07               ` Jens Axboe
2010-08-10 16:11                 ` Randy Dunlap
2010-08-10 16:14                   ` Jens Axboe
2010-08-10 16:34                     ` Randy Dunlap

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=4C5C69F9.5020108@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 \
    /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).