From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: devel@driverdev.osuosl.org,
Michael Turquette <mturquette@baylibre.com>,
Brendan Higgins <brendanhiggins@google.com>,
linux-kernel@vger.kernel.org, David Gow <davidgow@google.com>,
linux-clk@vger.kernel.org,
Soren Brinkmann <soren.brinkmann@xilinx.com>
Subject: Re: [PATCH] clk: staging: Specify IOMEM dependency for Xilinx Clocking Wizard driver
Date: Sun, 12 Jul 2020 08:49:09 +0200 [thread overview]
Message-ID: <20200712064909.GC2920853@kroah.com> (raw)
In-Reply-To: <159448501081.1987609.2376410636031633673@swboyd.mtv.corp.google.com>
On Sat, Jul 11, 2020 at 09:30:10AM -0700, Stephen Boyd wrote:
> Quoting David Gow (2020-06-29 21:45:17)
> > The Xilinx Clocking Wizard driver uses the devm_ioremap_resource
> > function, but does not specify a dependency on IOMEM in Kconfig. This
> > causes a build failure on architectures without IOMEM, for example, UML
> > (notably with make allyesconfig).
> >
> > Fix this by making CONFIG_COMMON_CLK_XLNX_CLKWZRD depend on CONFIG_IOMEM.
> >
> > Signed-off-by: David Gow <davidgow@google.com>
> > ---
>
> This driver is in the process of being destaged to drivers/clk/
>
> Greg, should I pick this one up?
Sure, if I haven't already.
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2020-07-12 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 4:45 [PATCH] clk: staging: Specify IOMEM dependency for Xilinx Clocking Wizard driver David Gow
2020-07-11 16:30 ` Stephen Boyd
2020-07-12 6:49 ` Greg Kroah-Hartman [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=20200712064909.GC2920853@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=soren.brinkmann@xilinx.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 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).