[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150930054439.GB17412@gmail.com>
Date: Wed, 30 Sep 2015 07:44:39 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: linux-tip-commits@...r.kernel.org, haiyangz@...rosoft.com,
stephen@...workplumber.org, kys@...rosoft.com,
gregkh@...uxfoundation.org, torvalds@...ux-foundation.org,
tglx@...utronix.de, jim.epost@...il.com, peterz@...radead.org,
hpa@...or.com, linux-kernel@...r.kernel.org,
tip-bot for Vitaly Kuznetsov <tipbot@...or.com>
Subject: Re: [tip:x86/urgent] x86/hyperv: Fix the build in the
CONFIG_KEXEC_CORE=y case
* Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> tip-bot for Vitaly Kuznetsov <tipbot@...or.com> writes:
>
> > Commit-ID: 7d381b749a010ccd48d5649c843cac0d14d1c229
> > Gitweb: http://git.kernel.org/tip/7d381b749a010ccd48d5649c843cac0d14d1c229
> > Author: Vitaly Kuznetsov <vkuznets@...hat.com>
> > AuthorDate: Wed, 23 Sep 2015 12:02:57 +0200
> > Committer: Ingo Molnar <mingo@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists