From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
Subject: Re: [PATCH] i2c: ocores: rework clk code to handle NULL cookie
Date: Fri, 20 Feb 2015 17:43:58 +0100 [thread overview]
Message-ID: <20150220164358.GB12246@katana> (raw)
In-Reply-To: <1424363824-6093-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Thu, Feb 19, 2015 at 05:37:04PM +0100, Wolfram Sang wrote:
> For, !HAVE_CLK the clk API returns a NULL cookie. Rework the
> initialization code to handle that. If clk_get_rate() delivers 0, we use
> the fallback mechanisms. The patch is pretty easy when ignoring white
> space issues (git diff -b).
>
> Suggested-by: Russell King <rmk+kernel-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
> Signed-off-by: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
> Cc: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Cc: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
Applied to for-next so this gets larger build-testing ASAP. Then, it can
be in my pull request today or tomorrow. We need it to avoid regressions
for !HAVE_CLK configs. HW tests would be really appreciated!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-20 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 16:37 [PATCH] i2c: ocores: rework clk code to handle NULL cookie Wolfram Sang
[not found] ` <1424363824-6093-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-02-20 16:43 ` Wolfram Sang [this message]
2015-02-20 16:51 ` Max Filippov
[not found] ` <CAMo8Bf+=Ny-uc+wmr9OsKh9kUhYqVXLw-nM4h+y_OMKx_FpCHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-20 17:00 ` Wolfram Sang
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=20150220164358.GB12246@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
--cc=jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.