From: Ingo Molnar <mingo@kernel.org>
To: Mathias Krause <minipli@googlemail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 0/2] x86, microcode: __ref / __refdata cleanups
Date: Mon, 20 Jul 2015 09:40:40 +0200 [thread overview]
Message-ID: <20150720074040.GB10802@gmail.com> (raw)
In-Reply-To: <1437326516-13689-1-git-send-email-minipli@googlemail.com>
* Mathias Krause <minipli@googlemail.com> wrote:
> Hi Boris,
>
> two small cleanups for wrongly annotated variables / functions. They
> used to require that annotation for __cpuinit but as that one is gone
> since v3.11 we can drop the __ref / __refdata annotation, too.
>
> Please apply.
>
>
> Mathias Krause (2):
> x86, microcode: Drop bogus __refdata annotation of cpu notifier
> x86, microcode: Drop bogus __ref annotation of show_saved_mc()
>
> arch/x86/kernel/cpu/microcode/core.c | 2 +-
> arch/x86/kernel/cpu/microcode/intel_early.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Please merge this into the single x86 patch of the previous series that gets rid
of __ref/__refdata. There's no need to create unnecessary churn.
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-20 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 17:21 [PATCH 0/2] x86, microcode: __ref / __refdata cleanups Mathias Krause
2015-07-19 17:21 ` [PATCH 1/2] x86, microcode: Drop bogus __refdata annotation of cpu notifier Mathias Krause
2015-07-19 17:21 ` [PATCH 2/2] x86, microcode: Drop bogus __ref annotation of show_saved_mc() Mathias Krause
2015-07-20 7:40 ` Ingo Molnar [this message]
2015-07-20 15:54 ` [PATCH 0/2] x86, microcode: __ref / __refdata cleanups Mathias Krause
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=20150720074040.GB10802@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=minipli@googlemail.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).