From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: kgdb-bugreport@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: KGDB: 8250_kgdb warnings
Date: Mon, 28 Jan 2008 11:19:33 +0100 [thread overview]
Message-ID: <479DAC35.60308@siemens.com> (raw)
Hi Jason,
so far I ignored this because it worked, but I know my customer will
complain later anyway: What is the deeper meaning of this warning which
shows up once per registered UART port on my (x86) boxes?
void kgdb8250_add_port(int i, struct uart_port *serial_req)
{
#ifdef CONFIG_KGDB_SIMPLE_SERIAL
if (should_copy_rs_table)
printk(KERN_ERR "8250_kgdb: warning will over write serial"
" port definitions at kgdb init time\n");
#endif
...
When I look at kgdb8250_add_platform_port, it starts with a call to
kgdb8250_copy_rs_table, and I'm wondering now if that wouldn't be more
appropriate here.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2008-01-28 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:19 Jan Kiszka [this message]
2008-01-29 22:55 ` [PATCH][KGDB] Re: [Kgdb-bugreport] " Jason Wessel
2008-01-29 23:21 ` [PATCH][KGDB] " Jan Kiszka
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=479DAC35.60308@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome