From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-serial@vger.kernel.org, akpm@linux-foundation.org,
alan@lxorguk.ukuu.org.uk, linux-mips@linux-mips.org,
Tomaso Paoletti <tpaoletti@caviumnetworks.com>
Subject: Re: [PATCH 5/5] Serial: UART driver changes for Cavium OCTEON.
Date: Tue, 02 Dec 2008 10:30:52 +0900 [thread overview]
Message-ID: <49348FCC.1050404@necel.com> (raw)
In-Reply-To: <4934303F.1000509@caviumnetworks.com>
David Daney wrote:
> ... All our boards are now working with no extra bug flags needed. So I
> will simplify this patch set by getting rid of UART_BUG_TIMEOUT.
Great! and makes sense. Thank you for taking care of my comments. I've
also checked the serial patches of version 2, and they looks in good
shape.
--
Shinya Kuribayashi
NEC Electronics
prev parent reply other threads:[~2008-12-02 1:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 0:14 [PATCH 0/5] serial: Patches for OCTEON CPU support David Daney
2008-11-26 0:18 ` [PATCH 1/5] 8250: Don't clobber spinlocks David Daney
2008-11-26 0:18 ` [PATCH 2/5] 8250: Serial driver changes to support future Cavium OCTEON serial patches David Daney
2008-11-26 0:18 ` [PATCH 3/5] Serial: Allow port type to be specified when calling serial8250_register_port David Daney
2008-11-26 0:18 ` [PATCH 4/5] 8250: Allow port type to specify bugs that are not probed for David Daney
2008-11-26 0:18 ` [PATCH 5/5] Serial: UART driver changes for Cavium OCTEON David Daney
2008-11-28 3:27 ` Shinya Kuribayashi
2008-12-01 18:43 ` David Daney
2008-12-02 1:30 ` Shinya Kuribayashi [this message]
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=49348FCC.1050404@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=tpaoletti@caviumnetworks.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.