On Tue 2020-09-01 12:24:51, Josh Poimboeuf wrote:
> On Thu, Aug 06, 2020 at 11:24:26AM +0200, Petr Mladek wrote:
> > On Tue 2020-07-21 13:17:00, Miroslav Benes wrote:
> > > On Fri, 17 Jul 2020, Josh Poimboeuf wrote:
> > >
> > > > Use of the new -flive-patching flag was introduced with the following
> > > > commit:
> > > >
> > > > 43bd3a95c98e ("kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled")
> > > >
> > > > This reverts commit 43bd3a95c98e1a86b8b55d97f745c224ecff02b9.
> > > >
> > > > Fixes: 43bd3a95c98e ("kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled")
> > > > Reported-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> > > > Signed-off-by: Josh Poimboeuf <jpoimboe@xxxxxxxxxx>
> > >
> > > Acked-by: Miroslav Benes <mbenes@xxxxxxx>
> >
> > Acked-by: Petr Mladek <pmladek@xxxxxxxx>
> >
> > Hmm, the patch has not been pushed into livepatching.git and is not
> > available in the pull request for 5.9.
> >
> > Is it OK to leave it for 5.10?
> > Or would you prefer to get it into 5.9 even on this stage?
> >
> > I personally do not mind. It depends how urgent it is for others.
>
> Sorry for leaving this question hanging. Let's go with 5.10 ;-)
The patch is committed in livepatch.git, branch
for-5.10/flive-patching.
Best Regards,
Petr
