From: Greg KH <gregkh@linuxfoundation.org>
To: Evalds Iodzevics <evalds.iodzevics@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: missing patch
Date: Mon, 1 Apr 2019 18:58:53 +0200 [thread overview]
Message-ID: <20190401165853.GA1929@kroah.com> (raw)
In-Reply-To: <20190401160629.GA20725@kroah.com>
On Mon, Apr 01, 2019 at 06:06:29PM +0200, Greg KH wrote:
> On Sat, Mar 30, 2019 at 06:13:16PM +0200, Evalds Iodzevics wrote:
> > Hi back in the December of 2016 there was commit
> > "1c52d859cb2d417e7216d3e56bb7fea88444cec9"
> >
> > witch was followed shortly by "c198b121b1a1d7a7171770c634cd49191bac4477"
> >
> > Unfortunately only the first commit was later included in long-term kernel
> > branches such as 4.4 and 4.9 witch left some of microcode functionality
> > broken on 32 bit systems
> >
> > I guess it should be easily fixed by including
> > "c198b121b1a1d7a7171770c634cd49191bac4477" in those branches
>
> Now queued up, thanks!
Hm, no, it causes a bunch of build warnings that look like things are
about to break:
arch/x86/kernel/alternative.o: warning: objtool: do_sync_core()+0x1b: unsupported instruction in callable function
arch/x86/kernel/alternative.o: warning: objtool: text_poke_early()+0x83: unsupported instruction in callable function
arch/x86/kernel/alternative.o: warning: objtool: apply_alternatives()+0x366: unsupported instruction in callable function
arch/x86/kernel/alternative.o: warning: objtool: text_poke()+0x196: unsupported instruction in callable function
So I'm going to drop this patch from both trees now. Can you provide a
working backported version, or find what else needs to be applied as
well for this patch?
thanks,
greg k-h
next prev parent reply other threads:[~2019-04-01 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 16:13 missing patch Evalds Iodzevics
2019-04-01 16:06 ` Greg KH
2019-04-01 16:58 ` Greg KH [this message]
2019-05-26 7:32 ` Evalds Iodzevics
2019-08-02 8:15 ` Greg KH
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=20190401165853.GA1929@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=evalds.iodzevics@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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.