From: Ingo Molnar <mingo@kernel.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: linux-tip-commits@vger.kernel.org, haiyangz@microsoft.com,
stephen@networkplumber.org, kys@microsoft.com,
gregkh@linuxfoundation.org, torvalds@linux-foundation.org,
tglx@linutronix.de, jim.epost@gmail.com, peterz@infradead.org,
hpa@zytor.com, linux-kernel@vger.kernel.org,
tip-bot for Vitaly Kuznetsov <tipbot@zytor.com>
Subject: Re: [tip:x86/urgent] x86/hyperv: Fix the build in the CONFIG_KEXEC_CORE=y case
Date: Wed, 30 Sep 2015 07:44:39 +0200 [thread overview]
Message-ID: <20150930054439.GB17412@gmail.com> (raw)
In-Reply-To: <87pp1130e8.fsf@vitty.brq.redhat.com>
* Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
> tip-bot for Vitaly Kuznetsov <tipbot@zytor.com> writes:
>
> > Commit-ID: 7d381b749a010ccd48d5649c843cac0d14d1c229
> > Gitweb: http://git.kernel.org/tip/7d381b749a010ccd48d5649c843cac0d14d1c229
> > Author: Vitaly Kuznetsov <vkuznets@redhat.com>
> > AuthorDate: Wed, 23 Sep 2015 12:02:57 +0200
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Tue, 29 Sep 2015 09:37:06 +0200
> >
> > x86/hyperv: Fix the build in the CONFIG_KEXEC_CORE=y case
>
> It was '!CONFIG_KEXEC_CORE' in the original patch so I'd expect to see
> 'CONFIG_KEXEC_CORE=n' here (if the '!' sign causes issues).
>
> [...]
Ok, fixed it up.
Thanks,
Ingo
next prev parent reply other threads:[~2015-09-30 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 10:02 [PATCH v3] x86: hyperv: fix build in !CONFIG_KEXEC_CORE case Vitaly Kuznetsov
2015-09-28 16:36 ` [tip:x86/urgent] x86: Hyperv: fix build in %21CONFIG_KEXEC_CORE case tip-bot for Vitaly Kuznetsov
2015-09-29 7:39 ` [tip:x86/urgent] x86/hyperv: Fix the build in the CONFIG_KEXEC_CORE=y case tip-bot for Vitaly Kuznetsov
2015-09-29 11:55 ` Vitaly Kuznetsov
2015-09-30 5:44 ` Ingo Molnar [this message]
2015-09-30 5:45 ` [tip:x86/urgent] x86/hyperv: Fix the build in the !CONFIG_KEXEC_CORE case tip-bot for Vitaly Kuznetsov
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=20150930054439.GB17412@gmail.com \
--to=mingo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jim.epost@gmail.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.org \
--cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.