From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: devel@driverdev.osuosl.org,
"J . German Rivera" <German.Rivera@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: fsl-mc: Do not allow building as a module
Date: Thu, 18 Feb 2016 20:36:35 -0800 [thread overview]
Message-ID: <20160219043635.GA8029@kroah.com> (raw)
In-Reply-To: <20160218140230.GC3941@ulmo.nvidia.com>
On Thu, Feb 18, 2016 at 03:02:30PM +0100, Thierry Reding wrote:
> On Mon, Feb 15, 2016 at 02:22:22PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > This driver uses functionality (MSI IRQ domain) whose symbols aren't
> > exported, and hence the modular build fails. While arguably there might
> > be reasons to make these symbols available to modules, that change would
> > be fairly involved and the set of exported functions should be carefully
> > auditioned. Fix the build failure for now by marking the driver boolean.
> >
> > Cc: J. German Rivera <German.Rivera@freescale.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > drivers/staging/fsl-mc/bus/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Sorry for being pushy, but this has had allmodconfig builds broken in
> linux-next for a couple of days now. The driver has been marked BROKEN
> now in linux-next to remedy that, but having proper fixes seems better
> than that.
Sorry for the delay, now merged, thanks.
greg k-h
prev parent reply other threads:[~2016-02-19 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 13:22 [PATCH 1/2] staging: fsl-mc: Do not allow building as a module Thierry Reding
2016-02-15 13:22 ` [PATCH 2/2] staging: fsl-mc: Avoid section mismatch Thierry Reding
2016-02-18 14:02 ` [PATCH 1/2] staging: fsl-mc: Do not allow building as a module Thierry Reding
2016-02-19 4:36 ` 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=20160219043635.GA8029@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=German.Rivera@freescale.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry.reding@gmail.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).