public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-kernel@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 01/11] drivers/crypto: include <module.h> for modular caam code
Date: Fri, 1 May 2015 09:40:04 -0400	[thread overview]
Message-ID: <55438234.7040205@windriver.com> (raw)
In-Reply-To: <20150501032404.GC371@gondor.apana.org.au>

On 15-04-30 11:24 PM, Herbert Xu wrote:
> On Thu, Apr 30, 2015 at 09:47:37PM -0400, Paul Gortmaker 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: Herbert Xu <herbert@gondor.apana.org.au>
>> Cc: "David S. Miller" <davem@davemloft.net>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> 
> Please post patches to linux-crypto@vger.kernel.org if you want them
> to go through the crypto tree.

Sure, I will add a CC for that in v2 if the patch is needed.

> 
> Also it actually gets module.h through caam/compat.h.  So your
> patch is unnecessary.

Well, in my original build testing this file failed to compile once
the modular code was moved from init.h to module.h as per the description
in the 0/11.

Perhaps since that testing something else has changed.  I will drop this
patch and retest and if it no longer fails, then great.

Thanks,
Paul.
--

> 
> Cheers,
> 

  reply	other threads:[~2015-05-01 13:41 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 [this message]
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
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=55438234.7040205@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.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