public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-mips <linux-mips@linux-mips.org>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH 21/26] Serial: Allow port type to be specified when calling serial8250_register_port.
Date: Thu, 20 Nov 2008 13:00:47 -0800	[thread overview]
Message-ID: <4925CFFF.9010502@caviumnetworks.com> (raw)
In-Reply-To: <20081120200256.73f98e09@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> On Tue, 18 Nov 2008 14:24:15 -0800
> David Daney <ddaney@caviumnetworks.com> wrote:
> 
>> Add flag value UPF_FIXED_TYPE which specifies that the UART type is
>> known and should not be probed.  For this case the UARTs properties
>> are just copied out of the uart_config entry.
> 
> Looks fine to me

Re-adding the lists...

Does that mean I an add Acked-by you to this patch?

David Daney

  parent reply	other threads:[~2008-11-20 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 22:21 [PATCH 00/26] Add Cavium OCTEON processor support (v4) David Daney
2008-11-18 22:24 ` [PATCH 19/26] 8250: Don't clobber spinlocks David Daney
2008-11-18 22:24 ` [PATCH 20/26] 8250: Serial driver changes to support future Cavium OCTEON serial patches David Daney
2008-11-20 20:02   ` Alan Cox
2008-11-18 22:24 ` [PATCH 21/26] Serial: Allow port type to be specified when calling serial8250_register_port David Daney
     [not found]   ` <20081120200256.73f98e09@lxorguk.ukuu.org.uk>
2008-11-20 21:00     ` David Daney [this message]
2008-11-18 22:24 ` [PATCH 22/26] 8250: Allow port type to specify bugs that are not probed for David Daney
2008-11-18 22:24 ` [PATCH 23/26] Serial: UART driver changes for Cavium OCTEON David Daney
2008-11-20 20:06   ` Alan Cox

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=4925CFFF.9010502@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-serial@vger.kernel.org \
    /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