From: Andrew Victor <andrew@sanpeople.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/8] at91_serial -> atmel_serial: Kconfig symbols
Date: 28 Sep 2006 10:34:49 +0200 [thread overview]
Message-ID: <1159432488.23157.25.camel@fuzzie.sanpeople.com> (raw)
In-Reply-To: <11593762851735-git-send-email-hskinnemoen@atmel.com>
hi Haavard,
> Rename the following Kconfig symbols:
> * CONFIG_SERIAL_AT91 -> CONFIG_SERIAL_ATMEL
> * CONFIG_SERIAL_AT91_CONSOLE -> CONFIG_SERIAL_ATMEL_CONSOLE
> * CONFIG_SERIAL_AT91_TTYAT -> CONFIG_SERIAL_ATMEL_TTYAT
> -config SERIAL_AT91
> - bool "AT91RM9200 / AT91SAM9261 serial port support"
> +config SERIAL_ATMEL
> + bool "AT91 / AT32 on-chip serial port support"
> depends on ARM && (ARCH_AT91RM9200 || ARCH_AT91SAM9261)
> select SERIAL_CORE
> help
> This enables the driver for the on-chip UARTs of the Atmel
> AT91RM9200 and AT91SAM926 processor.
Shouldn't this dependency be:
depends on (ARM && ARCH_AT91) || AVR32
(The "ARCH_AT91RM9200 || ARCH_AT91SAM9261" can be replaced with
ARCH_AT91 since the driver should usable on the RM9200, SAM9261 and
SAM9260)
The help text should probably also be updated for these 3 options so
that it mentions the AVR32.
Regards,
Andrew Victor
next prev parent reply other threads:[~2006-09-28 8:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 16:57 [PATCH 0/8] Rename at91_serial driver as atmel_serial Haavard Skinnemoen
2006-09-27 16:57 ` [PATCH 1/8] at91_serial -> atmel_serial: at91rm9200_usart.h Haavard Skinnemoen
2006-09-27 16:57 ` [PATCH 2/8] at91_serial -> atmel_serial: at91_serial.c Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 3/8] at91_serial -> atmel_serial: Kconfig symbols Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 4/8] at91_serial -> atmel_serial: Platform device name Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 5/8] at91_serial -> atmel_serial: Public definitions Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 6/8] at91_serial -> atmel_serial: Internal names Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 7/8] serial: Rename PORT_AT91 -> PORT_ATMEL Haavard Skinnemoen
2006-09-27 16:58 ` [PATCH 8/8] atmel_serial: Kill at91_register_uart_fns Haavard Skinnemoen
2006-09-28 9:21 ` Andrew Victor
2006-09-28 9:38 ` Haavard Skinnemoen
2006-09-28 11:14 ` Andrew Victor
2006-09-28 11:51 ` Haavard Skinnemoen
2006-09-28 11:56 ` Andrew Victor
2006-09-28 17:02 ` Sam Ravnborg
2006-09-28 9:03 ` [PATCH 7/8] serial: Rename PORT_AT91 -> PORT_ATMEL Andrew Victor
2006-09-28 9:02 ` [PATCH 6/8] at91_serial -> atmel_serial: Internal names Andrew Victor
2006-09-28 8:54 ` [PATCH 5/8] at91_serial -> atmel_serial: Public definitions Andrew Victor
2006-09-28 9:24 ` Haavard Skinnemoen
2006-09-28 9:22 ` Andrew Victor
2006-09-28 8:35 ` [PATCH 4/8] at91_serial -> atmel_serial: Platform device name Andrew Victor
2006-09-28 12:55 ` Haavard Skinnemoen
2006-09-28 8:34 ` Andrew Victor [this message]
2006-09-28 8:54 ` [PATCH 3/8] at91_serial -> atmel_serial: Kconfig symbols Haavard Skinnemoen
2006-09-28 8:50 ` Andrew Victor
2006-09-28 8:22 ` [PATCH 2/8] at91_serial -> atmel_serial: at91_serial.c Andrew Victor
2006-09-28 8:20 ` [PATCH 1/8] at91_serial -> atmel_serial: at91rm9200_usart.h Andrew Victor
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=1159432488.23157.25.camel@fuzzie.sanpeople.com \
--to=andrew@sanpeople.com \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@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
all inboxes | Powered by JetHome®