From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org> To: Leo Yan <leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Cc: Wei Xu <xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>, Dan Zhao <dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>, zhenwei.wang-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org, Haojian Zhuang <haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>, Bintian Wang <bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>, mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH 1/4] clk: hisi: add API for allocation clk data struct Date: Thu, 26 Mar 2015 14:18:34 +0000 [thread overview] Message-ID: <20150326141834.GI8656@n2100.arm.linux.org.uk> (raw) In-Reply-To: <1427368419-22222-2-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> On Thu, Mar 26, 2015 at 07:13:36PM +0800, Leo Yan wrote: > +struct hisi_clock_data __init *hisi_clk_init(struct device_node *np, > + int nr_clks) > +{ > + struct hisi_clock_data *clk_data; > + void __iomem *base; > + > + if (np) { > + base = of_iomap(np, 0); > + if (!base) { > + pr_err("failed to map Hisilicon clock registers\n"); > + return NULL; > + } > + printk("%s: base %p\n", __func__, base); Did you leave your debugging in? > + } else { > + pr_err("failed to find Hisilicon clock node in DTS\n"); > + return NULL; > + } I know you're mostly only moving this code, but it would be far better if it were written: if (!np) { pr_err("failed to find Hisilicon clock node in DTS\n"); return NULL; } base = of_iomap(np, 0); if (!base) { pr_err("failed to map Hisilicon clock registers\n"); return NULL; } Possibly do this first as a separate patch, and then move the code. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/4] clk: hisi: add API for allocation clk data struct Date: Thu, 26 Mar 2015 14:18:34 +0000 [thread overview] Message-ID: <20150326141834.GI8656@n2100.arm.linux.org.uk> (raw) In-Reply-To: <1427368419-22222-2-git-send-email-leo.yan@linaro.org> On Thu, Mar 26, 2015 at 07:13:36PM +0800, Leo Yan wrote: > +struct hisi_clock_data __init *hisi_clk_init(struct device_node *np, > + int nr_clks) > +{ > + struct hisi_clock_data *clk_data; > + void __iomem *base; > + > + if (np) { > + base = of_iomap(np, 0); > + if (!base) { > + pr_err("failed to map Hisilicon clock registers\n"); > + return NULL; > + } > + printk("%s: base %p\n", __func__, base); Did you leave your debugging in? > + } else { > + pr_err("failed to find Hisilicon clock node in DTS\n"); > + return NULL; > + } I know you're mostly only moving this code, but it would be far better if it were written: if (!np) { pr_err("failed to find Hisilicon clock node in DTS\n"); return NULL; } base = of_iomap(np, 0); if (!base) { pr_err("failed to map Hisilicon clock registers\n"); return NULL; } Possibly do this first as a separate patch, and then move the code. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net.
next prev parent reply other threads:[~2015-03-26 14:18 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-26 11:13 [PATCH 0/4] clk: hisilicon: support stub clock Leo Yan 2015-03-26 11:13 ` Leo Yan [not found] ` <1427368419-22222-1-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2015-03-26 11:13 ` [PATCH 1/4] clk: hisi: add API for allocation clk data struct Leo Yan 2015-03-26 11:13 ` Leo Yan [not found] ` <1427368419-22222-2-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2015-03-26 14:18 ` Russell King - ARM Linux [this message] 2015-03-26 14:18 ` Russell King - ARM Linux [not found] ` <20150326141834.GI8656-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org> 2015-03-27 1:48 ` Leo Yan 2015-03-27 1:48 ` Leo Yan 2015-03-26 11:13 ` [PATCH 2/4] dt-bindings: clk: hisilicon: Document stub clock driver Leo Yan 2015-03-26 11:13 ` Leo Yan 2015-03-26 11:13 ` [PATCH 3/4] clk: hisi: add stub clk driver Leo Yan 2015-03-26 11:13 ` Leo Yan [not found] ` <1427368419-22222-4-git-send-email-leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2015-03-26 14:22 ` Russell King - ARM Linux 2015-03-26 14:22 ` Russell King - ARM Linux [not found] ` <20150326142226.GJ8656-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org> 2015-03-27 2:08 ` Leo Yan 2015-03-27 2:08 ` Leo Yan 2015-03-26 11:13 ` [PATCH 4/4] clk: hisi: add stub clock register function Leo Yan 2015-03-26 11:13 ` Leo Yan
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=20150326141834.GI8656@n2100.arm.linux.org.uk \ --to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \ --cc=bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \ --cc=dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=haojian.zhuang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=leo.yan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=xuwei5-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \ --cc=zhenwei.wang-C8/M+/jPZTeaMJb+Lgu22Q@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: linkBe 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.