From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Michael Spang <spang@chromium.org>, Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-serial@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
arnd@arndb.de
Subject: S3C64xx serial broken in -next
Date: Thu, 18 Apr 2013 13:56:26 +0100 [thread overview]
Message-ID: <20130418125625.GF13687@opensource.wolfsonmicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
I'm seeing lots of dropped characters from the s3c64xx serial driver in
something closely resmbling -next today, it seemed fine yesterday. Not
100% sure that this is the serial driver itself but reverting 38adbc
(serial: samsung: Avoid waiting forever for TX ready) seems to improve
things a bit.
I'm not seeing any obvious changes in the arch code recently, the serial
driver looks like the most recently updated thing though that wasn't
today either.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-04-18 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 12:56 Mark Brown [this message]
2013-04-18 14:01 ` S3C64xx serial broken in -next Mark Brown
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=20130418125625.GF13687@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=spang@chromium.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;
as well as URLs for NNTP newsgroup(s).