From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wolfram Sang <wsa@the-dreams.de>, linux-kernel@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 2/6] net: ethernet: renesas: ravb_main: test clock rate to avoid division by 0
Date: Mon, 4 Apr 2016 01:28:44 +0300 [thread overview]
Message-ID: <5701991C.4020904@cogentembedded.com> (raw)
In-Reply-To: <20160403213641.GA24129@katana>
On 04/04/2016 12:36 AM, Wolfram Sang wrote:
>> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>
>> The clk API may return 0 on clk_get_rate, so we should check the result before
>> using it as a divisor.
>>
>> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Ping.
http://patchwork.ozlabs.org/patch/591160/
I have no idea why it's marked this way... Dave?
MBR, Sergei
next prev parent reply other threads:[~2016-04-03 22:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 22:33 [PATCH 0/6] treewide: test clock rate to avoid division by 0 Wolfram Sang
2016-03-02 22:33 ` Wolfram Sang
2016-03-02 22:33 ` [PATCH 1/6] ide: palm_bk3710: " Wolfram Sang
2016-03-02 22:33 ` [PATCH 2/6] net: ethernet: renesas: ravb_main: " Wolfram Sang
2016-03-03 11:14 ` Sergei Shtylyov
2016-04-03 21:36 ` Wolfram Sang
2016-04-03 22:28 ` Sergei Shtylyov [this message]
2016-03-02 22:33 ` [PATCH 3/6] pwm: pwm-img: " Wolfram Sang
2016-03-04 15:01 ` Thierry Reding
2016-03-02 22:33 ` [PATCH 4/6] pwm: pwm-lpc18xx-sct: " Wolfram Sang
2016-03-02 22:33 ` Wolfram Sang
2016-03-02 22:33 ` Wolfram Sang
2016-03-02 22:44 ` Joachim Eastwood
2016-03-02 22:44 ` Joachim Eastwood
2016-03-02 22:58 ` Wolfram Sang
2016-03-02 22:58 ` Wolfram Sang
2016-03-02 22:33 ` [PATCH 5/6] watchdog: atlas7_wdt: " Wolfram Sang
2016-03-03 4:25 ` Guenter Roeck
2016-03-06 9:09 ` Wim Van Sebroeck
2016-03-02 22:33 ` [PATCH 6/6] watchdog: tangox_wdt: " Wolfram Sang
2016-03-03 4:26 ` Guenter Roeck
2016-03-03 8:12 ` 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=5701991C.4020904@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wsa@the-dreams.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 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.