From: Daniel Thompson <daniel.thompson@linaro.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, spear-devel@list.st.com,
Arnd Bergmann <arnd@arndb.de>, Paul Bolle <pebolle@tiscali.nl>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
patches@linaro.org, linaro-kernel@lists.linaro.org,
Tony Lindgren <tony@atomide.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v12 11/15] arm: omap1: Migrate debug_ll macros to use 8250.S
Date: Mon, 17 Nov 2014 09:07:36 +0000 [thread overview]
Message-ID: <5469BAD8.3090006@linaro.org> (raw)
In-Reply-To: <20141116002956.GA13220@fuloong-minipc.musicnaut.iki.fi>
On 16/11/14 00:29, Aaro Koskinen wrote:
> Hi,
>
> On Fri, Oct 24, 2014 at 11:54:32AM +0100, Daniel Thompson wrote:
>> + config DEBUG_OMAP1UART1
>> + bool "Kernel low-level debugging via OMAP1 UART1"
>> + depends on ARCH_OMAP1
>> + select DEBUG_UART_8250
>> + help
>> + Say Y here if you want kernel low-level debugging support
>> + on OMAP1 based platforms (expect OMAP730) on the UART1.
> [...]
>> + on OMAP1 based platforms (expect OMAP730) on the UART2.
> [...]
>> + on OMAP1 based platforms (expect OMAP730) on the UART3.
> ^^^^^^
>
> Spelling again wrong. I think it was already corrected in v11?
Sorry and, yes, you're right this was corrected in v11.
I was travelling when I posted v11 so I guess I must have forgot to pull
the right branches to my main machine. I will dig it and diff shortly to
make sure I didn't miss anything else.
Daniel.
next prev parent reply other threads:[~2014-11-17 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1414148076-12685-1-git-send-email-daniel.thompson@linaro.org>
2014-10-24 10:54 ` [PATCH v12 11/15] arm: omap1: Migrate debug_ll macros to use 8250.S Daniel Thompson
2014-11-16 0:29 ` Aaro Koskinen
2014-11-17 9:07 ` Daniel Thompson [this message]
2014-11-17 14:24 ` Daniel Thompson
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=5469BAD8.3090006@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=aaro.koskinen@iki.fi \
--cc=arnd.bergmann@linaro.org \
--cc=arnd@arndb.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=spear-devel@list.st.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tony@atomide.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 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).