From: Borislav Petkov <bp@alien8.de>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
kbuild-all@01.org, Borislav Petkov <bp@suse.de>,
Doug Thompson <dougthompson@xmission.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bp] EDAC, mce_amd_inj: inj_type can be static
Date: Fri, 5 Jun 2015 15:33:27 +0200 [thread overview]
Message-ID: <20150605133327.GG3679@pd.tnic> (raw)
In-Reply-To: <20150605112426.GA97073@lkp-sb04>
On Fri, Jun 05, 2015 at 07:24:26PM +0800, kbuild test robot wrote:
>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> mce_amd_inj.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/edac/mce_amd_inj.c b/drivers/edac/mce_amd_inj.c
> index 2a0c829..46a6b0e 100644
> --- a/drivers/edac/mce_amd_inj.c
> +++ b/drivers/edac/mce_amd_inj.c
> @@ -44,7 +44,7 @@ static const char * const flags_options[] = {
> };
>
> /* Set default injection to SW_INJ */
> -enum injection_type inj_type = SW_INJ;
> +static enum injection_type inj_type = SW_INJ;
>
> #define MCE_INJECT_SET(reg) \
> static int inj_##reg##_set(void *data, u64 val) \
Thanks kbuild test robot, applied!
:-D
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-06-05 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 11:24 [bp:for-next 15/22] drivers/edac/mce_amd_inj.c:47:21: sparse: symbol 'inj_type' was not declared. Should it be static? kbuild test robot
2015-06-05 11:24 ` [PATCH bp] EDAC, mce_amd_inj: inj_type can be static kbuild test robot
2015-06-05 13:33 ` Borislav Petkov [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=20150605133327.GG3679@pd.tnic \
--to=bp@alien8.de \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@suse.de \
--cc=dougthompson@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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