From: Thierry Reding <treding@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] serial: ns16550: Handle -ENOENT when requesting clock
Date: Tue, 4 Oct 2016 14:37:20 +0200 [thread overview]
Message-ID: <20161004123719.GA19913@ulmo.ba.sec> (raw)
In-Reply-To: <7926457f-221b-4991-905d-8ecf58f9d64c@wwwdotorg.org>
On Mon, Oct 03, 2016 at 10:23:49AM -0600, Stephen Warren wrote:
> On 09/30/2016 02:37 AM, Alexandre Courbot wrote:
> > When calling clk_get_by_index(), fall back to the legacy method of
> > getting the clock if -ENOENT is returned.
>
> Tested-by: Stephen Warren <swarren@nvidia.com>
Agreed, this looks like the more correct fix in retrospect.
Acked-by: Thierry Reding <treding@nvidia.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161004/38ceb2d4/attachment.sig>
next prev parent reply other threads:[~2016-10-04 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 8:37 [U-Boot] [PATCH] serial: ns16550: Handle -ENOENT when requesting clock Alexandre Courbot
2016-09-30 8:54 ` Alexandre Courbot
2016-10-03 16:23 ` Stephen Warren
2016-10-04 12:37 ` Thierry Reding [this message]
2016-10-07 0:32 ` [U-Boot] " Tom Rini
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=20161004123719.GA19913@ulmo.ba.sec \
--to=treding@nvidia.com \
--cc=u-boot@lists.denx.de \
/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