mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jongsung Kim" <neidhard.kim@lge.com>
To: "'Russell King - ARM Linux'" <linux@arm.linux.org.uk>
Cc: <gregkh@linuxfoundation.org>, <jslaby@suse.cz>,
	<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [RESEND][PATCH] ARM: PL011: add support for extended FIFO-size	of PL011-r1p5
Date: Mon, 22 Apr 2013 11:24:18 +0900	[thread overview]
Message-ID: <019701ce3f00$7e0c5390$7a24fab0$@lge.com> (raw)
In-Reply-To: <20130419141748.GU14496@n2100.arm.linux.org.uk>

Thank you for your comments, Russell. I'll happily apply your recommendation
just after it come up to the merge window. Or, do you want me to send it by now?

-----Original Message-----
From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk] 
Sent: Friday, April 19, 2013 11:18 PM
To: Jongsung Kim
Cc: gregkh@linuxfoundation.org; jslaby@suse.cz; linux-serial@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][PATCH] ARM: PL011: add support for extended FIFO-size of
PL011-r1p5

On Mon, Apr 15, 2013 at 02:45:25PM +0900, Jongsung Kim wrote:
> The latest r1p5-revision of the ARM PL011 UART has 32-byte FIFOs,
> while all earlier ones have 16-byte FIFOs. This patch suggests
> a way to set the FIFO-size correctly & flexibly by using a member
> function named get_fifosize, rather than using the fifosize member
> variable. The function takes the UARTPeriphID, and returns the
> correct FIFO size.

Same comments as previous version.


  reply	other threads:[~2013-04-22  2:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  5:45 Jongsung Kim
2013-04-19 14:17 ` Russell King - ARM Linux
2013-04-22  2:24   ` Jongsung Kim [this message]
2013-04-22 17:36     ` Russell King - ARM Linux
2013-04-20 13:31 ` Linus Walleij
2013-04-21  8:54   ` Russell King - ARM Linux

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='019701ce3f00$7e0c5390$7a24fab0$@lge.com' \
    --to=neidhard.kim@lge.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@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®