From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Bunch of serial warnings in next at least with omap-serial
Date: Tue, 3 May 2016 14:58:21 -0700 [thread overview]
Message-ID: <20160503215821.GR5995@atomide.com> (raw)
In-Reply-To: <572911BF.8000803@hurleysoftware.com>
* Peter Hurley <peter@hurleysoftware.com> [160503 14:03]:
> Hi Tony,
>
> On 05/03/2016 01:39 PM, Tony Lindgren wrote:
> > Hi Peter,
> >
> > Looks like probably commit 4047b37122d1 ("serial: core: Prevent unsafe
> > uart port access, part 1") in Linux next causes tons of warnings with at
> > least omap-serial. It does not revert cleanly I have not tested with that
> > reverted. Any ideas? Dmesg output of the errors below.
>
> Thanks for the report.
> Patch below should fix that.
Yes thanks that fixes it:
Tested-by: Tony Lindgren <tony@atomide.com>
prev parent reply other threads:[~2016-05-03 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160503203930.GQ5995@atomide.com>
2016-05-03 21:01 ` Bunch of serial warnings in next at least with omap-serial Peter Hurley
2016-05-03 21:58 ` Tony Lindgren [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=20160503215821.GR5995@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).