From: Ray Jui <rjui@broadcom.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Scott Branden <sbranden@broadcom.com>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 0/2] iProc clock driver fixes
Date: Mon, 29 Jun 2015 14:32:45 -0700 [thread overview]
Message-ID: <5591B97D.2080003@broadcom.com> (raw)
In-Reply-To: <1435613410-18698-1-git-send-email-rjui@broadcom.com>
To Michael's new email.
On 6/29/2015 2:30 PM, Ray Jui wrote:
> This patch series fixes two issues in the Broadcom iProc clock driver,
> reported by Dan Carpenter <dan.carpenter@oracle.com>: 1) a memory leak from
> the clock names; 2) 32-bit/64-bit arithmetic
>
> Code base used is the latest linux-next (20150629) and its GITHUB link is:
> https://github.com/Broadcom/cygnus-linux/tree/iproc-clk-misc-fix-v1
>
> Ray Jui (2):
> clk: iproc: fix memory leak from clock name
> clk: iproc: fix bit manipulation arithmetic
>
> drivers/clk/bcm/clk-iproc-asiu.c | 6 +-----
> drivers/clk/bcm/clk-iproc-pll.c | 13 ++++---------
> 2 files changed, 5 insertions(+), 14 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] iProc clock driver fixes
Date: Mon, 29 Jun 2015 14:32:45 -0700 [thread overview]
Message-ID: <5591B97D.2080003@broadcom.com> (raw)
In-Reply-To: <1435613410-18698-1-git-send-email-rjui@broadcom.com>
To Michael's new email.
On 6/29/2015 2:30 PM, Ray Jui wrote:
> This patch series fixes two issues in the Broadcom iProc clock driver,
> reported by Dan Carpenter <dan.carpenter@oracle.com>: 1) a memory leak from
> the clock names; 2) 32-bit/64-bit arithmetic
>
> Code base used is the latest linux-next (20150629) and its GITHUB link is:
> https://github.com/Broadcom/cygnus-linux/tree/iproc-clk-misc-fix-v1
>
> Ray Jui (2):
> clk: iproc: fix memory leak from clock name
> clk: iproc: fix bit manipulation arithmetic
>
> drivers/clk/bcm/clk-iproc-asiu.c | 6 +-----
> drivers/clk/bcm/clk-iproc-pll.c | 13 ++++---------
> 2 files changed, 5 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2015-06-29 21:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 21:30 [PATCH 0/2] iProc clock driver fixes Ray Jui
2015-06-29 21:30 ` Ray Jui
2015-06-29 21:30 ` [PATCH 1/2] clk: iproc: fix memory leak from clock name Ray Jui
2015-06-29 21:30 ` Ray Jui
2015-06-29 21:33 ` Ray Jui
2015-06-29 21:33 ` Ray Jui
2015-06-29 21:30 ` [PATCH 2/2] clk: iproc: fix bit manipulation arithmetic Ray Jui
2015-06-29 21:30 ` Ray Jui
2015-06-29 21:33 ` Ray Jui
2015-06-29 21:33 ` Ray Jui
2015-06-29 21:32 ` Ray Jui [this message]
2015-06-29 21:32 ` [PATCH 0/2] iProc clock driver fixes Ray Jui
2015-07-02 16:56 ` Stephen Boyd
2015-07-02 16:56 ` Stephen Boyd
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=5591B97D.2080003@broadcom.com \
--to=rjui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sbranden@broadcom.com \
/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.