From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: linux-serial@vger.kernel.org
Cc: philippe.langlais@stericsson.com
Subject: serial.h v serial_core.h PORT_ defines?
Date: Fri, 27 Aug 2010 20:35:41 +0100 [thread overview]
Message-ID: <20100827193541.GA29541@gallifrey> (raw)
Hi,
I was playing with sparse and it flagged that in drivers/serial/8250.c
there is a duplicate initialiser in the uart_config[] array
(from Linus's git):
[PORT_NS16550A] = {
.name = "NS16550A",
.fifo_size = 16,
.tx_loadsz = 16,
.fcr = UART_FCR_ENABLE_FIFO | UART_FCR_R_TRIG_10,
.flags = UART_CAP_FIFO | UART_NATSEMI,
},
and
[PORT_U6_16550A] = {
.name = "U6_16550A",
.fifo_size = 64,
.tx_loadsz = 64,
.fcr = UART_FCR_ENABLE_FIFO | UART_FCR_R_TRIG_10,
.flags = UART_CAP_FIFO | UART_CAP_AFE,
},
now PORT_NS16550A is defined as 14 in serial_core.h:
#define PORT_NS16550A 14
and PORT_U6_16550A is defined as 14 in serial.h:
235dae5d (Philippe Langlais 2010-07-29 17:13:57 +0200 80) #define PORT_U6_16550A 14
I guess that might subtly break NS16550A users?
My assumption is that Philippe's addition should actually
be to the serial_core.h list which currently goes upto 18.
However, that leaves the question of why is there a set of nearly
but not quite idential defines in serial.h and serial_core.h?
(please leave me on cc for replies)
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next reply other threads:[~2010-08-27 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 19:35 Dr. David Alan Gilbert [this message]
2010-08-31 11:55 ` serial.h v serial_core.h PORT_ defines? Philippe Langlais
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=20100827193541.GA29541@gallifrey \
--to=linux@treblig.org \
--cc=linux-serial@vger.kernel.org \
--cc=philippe.langlais@stericsson.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 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.