From: Linus Walleij <linus.walleij@linaro.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 03/11] drivers/gpio: include <module.h> for modular crystalcove code
Date: Tue, 12 May 2015 09:38:07 +0200 [thread overview]
Message-ID: <CACRpkdZ3sfVeSj=b=L5izwiV8yhFw-+AN4OJriuiU4Ft5J-tMQ@mail.gmail.com> (raw)
In-Reply-To: <1430444867-22342-4-git-send-email-paul.gortmaker@windriver.com>
On Fri, May 1, 2015 at 3:47 AM, Paul Gortmaker
<paul.gortmaker@windriver.com> wrote:
> This file is built off of a tristate Kconfig option and also contains
> modular function calls so it should explicitly include module.h to
> avoid compile breakage during header shuffles done in the future.
>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Alexandre Courbot <gnurou@gmail.com>
> Cc: linux-gpio@vger.kernel.org
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Patch applied.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-05-12 7:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 1:47 [PATCH 00/11] Fix implicit includes of <module.h> that will break Paul Gortmaker
2015-05-01 1:47 ` [PATCH 01/11] drivers/crypto: include <module.h> for modular caam code Paul Gortmaker
2015-05-01 3:24 ` Herbert Xu
2015-05-01 13:40 ` Paul Gortmaker
2015-05-01 1:47 ` [PATCH 02/11] drivers/clk: include <module.h> for clk-max77xxx modular code Paul Gortmaker
2015-05-01 21:37 ` Stephen Boyd
2015-05-02 0:29 ` Paul Gortmaker
2015-05-01 1:47 ` [PATCH 03/11] drivers/gpio: include <module.h> for modular crystalcove code Paul Gortmaker
2015-05-12 7:38 ` Linus Walleij [this message]
2015-05-01 1:47 ` [PATCH 04/11] drivers/gpu: include <module.h> for modular rockchip code Paul Gortmaker
2015-05-01 1:47 ` [PATCH 05/11] drivers/hsi: include <module.h> for modular omap_ssi code Paul Gortmaker
2015-05-01 1:47 ` [PATCH 06/11] drivers/net: include <module.h> for modular stmmac_platform code Paul Gortmaker
2015-05-04 3:40 ` David Miller
2015-05-01 1:47 ` [PATCH 07/11] drivers/pcmcia: include <module.h> for modular xxs1500_ss code Paul Gortmaker
2015-05-04 9:32 ` Wolfram Sang
2015-05-01 1:47 ` [PATCH 08/11] drivers/pcmcia: include <module.h> for modular max77802 code Paul Gortmaker
2015-05-01 10:11 ` Mark Brown
2015-05-01 13:34 ` Paul Gortmaker
2015-05-01 14:04 ` Mark Brown
2015-05-01 1:47 ` [PATCH 09/11] drivers/scsi: include <module.h> for modular ufshcd-pltfrm code Paul Gortmaker
2015-05-01 2:35 ` James Bottomley
2015-05-01 13:37 ` Paul Gortmaker
2015-05-01 13:43 ` James Bottomley
2015-05-01 1:47 ` [PATCH 10/11] drivers/staging: include <module.h> for modular android tegra_ion code Paul Gortmaker
2015-05-01 1:47 ` [PATCH 11/11] sh: mach-highlander/psw.c is tristate and should use module.h Paul Gortmaker
2015-06-03 21:18 ` [PATCH] drivers/cpufreq: include <module.h> for modular exynos-cpufreq.c code Paul Gortmaker
2015-06-04 2:00 ` Krzysztof Kozlowski
2015-06-04 2:32 ` Viresh Kumar
2015-06-15 23:47 ` Rafael J. Wysocki
2015-06-15 23:53 ` Krzysztof Kozlowski
2015-06-16 3:28 ` Paul Gortmaker
2015-06-16 15:29 ` Paul Gortmaker
2015-06-17 0:36 ` Krzysztof Kozlowski
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='CACRpkdZ3sfVeSj=b=L5izwiV8yhFw-+AN4OJriuiU4Ft5J-tMQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.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).