From: Yuki Cuss <celtic@sairyx.org>
To: David Vrabel <dvrabel@arcom.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial: SERIAL_8250_RUNTIME_UARTS must be <= SERIAL_8250_NR_UARTS
Date: Mon, 06 Feb 2006 21:42:19 +1100 [thread overview]
Message-ID: <43E7280B.6060607@sairyx.org> (raw)
In-Reply-To: <43E72479.4020804@arcom.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
David Vrabel wrote:
>If SERIAL_8250_RUNTIME_UARTS is > SERIAL_8250_NR_UARTS then more serial
>ports are registered than we've allocated memory for. Prevent this by
>limiting SERIAL_8250_RUNTIME_UARTS in the serial Kconfig.
>
>Signed-off-by: David Vrabel <dvrabel@arcom.com>
>
>
Is there any real use case for having *less* registered serial ports and
having some spare?
- Yuki.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2917 bytes --]
next prev parent reply other threads:[~2006-02-06 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 10:27 serial: SERIAL_8250_RUNTIME_UARTS must be <= SERIAL_8250_NR_UARTS David Vrabel
2006-02-06 10:42 ` Yuki Cuss [this message]
2006-02-06 19:41 ` Dave Jones
2006-02-06 10:59 ` David Vrabel
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=43E7280B.6060607@sairyx.org \
--to=celtic@sairyx.org \
--cc=dvrabel@arcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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