From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: zynq: remove redundant $(CONFIG_ARCH_ZYNQ) in Makefile
Date: Mon, 27 Jul 2015 10:21:35 +0200 [thread overview]
Message-ID: <55B5EA0F.8000404@monstr.eu> (raw)
In-Reply-To: <1437982602-26886-1-git-send-email-yamada.masahiro@socionext.com>
On 07/27/2015 09:36 AM, Masahiro Yamada wrote:
> Kbuild descends into drivers/clk/zynq/ only when CONFIG_ARCH_ZYNQ
> is enabled. (see drivers/clk/Makefile)
>
> $(CONFIG_ARCH_ZYNQ) in drivers/clk/zynq/Makefile always evaluates
> to 'y'.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> drivers/clk/zynq/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/zynq/Makefile b/drivers/clk/zynq/Makefile
> index 156d923..0afc2e7 100644
> --- a/drivers/clk/zynq/Makefile
> +++ b/drivers/clk/zynq/Makefile
> @@ -1,3 +1,3 @@
> # Zynq clock specific Makefile
>
> -obj-$(CONFIG_ARCH_ZYNQ) += clkc.o pll.o
> +obj-y += clkc.o pll.o
>
Applied to zynq/soc branch and will go to mainline via arm-soc.
Let me know if someone else wants to take it via different tree.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150727/73cb0d26/attachment.sig>
prev parent reply other threads:[~2015-07-27 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 7:36 [PATCH] clk: zynq: remove redundant $(CONFIG_ARCH_ZYNQ) in Makefile Masahiro Yamada
2015-07-27 8:21 ` Michal Simek [this message]
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=55B5EA0F.8000404@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).