On Wed, Sep 12, 2018 at 05:36:23PM +0200, Vasily Gorbik wrote:
On Tue, Sep 11, 2018 at 12:14:30PM +0200, gregkh@linuxfoundation.org wrote:
This is a note to let you know that I've just added the patch titled
tracing: Handle CC_FLAGS_FTRACE more accuratelyto the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
...
to the 4.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
...
to the 4.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
...
to the 4.9-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git%3Ba=su...
I believe there is no need to backport this patch in neither of stable branches listed above. This patch is the first one in the patch series: http://lkml.kernel.org/r/cover.thread-aa7b8d.your-ad-here.call-01533557518-e...
The patch series adds s390 support for utilizing newly available for s390 in gcc 9 flags -fentry -mrecord-mcount and -mnop-mcount, and adds generic -mnop-mcount support. And there is no benefit in backporting just the first one.
Moreover this patch cause kernel recompile for intdeb-pkg and tar%pkg targets (i.e. make targz-pkg), because those targets call make recursively (they do extra "make modules_install"), and exported variable cause duplicated build flags in sub-make.
There is a potential fix: https://www.spinics.net/lists/linux-kbuild/msg19297.html
Thanks for letting me know, I've dropped this from everywhere now.
greg k-h