From: Greg KH <gregkh@linuxfoundation.org>
To: Vasily Gorbik <gor@linux.ibm.com>
Cc: alexander.levin@microsoft.com, rostedt@goodmis.org,
stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "tracing: Handle CC_FLAGS_FTRACE more accurately" has been added to the ...-stable tree
Date: Wed, 12 Sep 2018 20:24:28 +0200 [thread overview]
Message-ID: <20180912182428.GA20855@kroah.com> (raw)
In-Reply-To: <your-ad-here.call-01536766582-ext-7501@work.hours>
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 accurately
> >
> > to the 4.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> ...
>
> > to the 4.18-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> ...
>
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> ...
>
> > to the 4.9-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
>
> 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-ext-9465@work.hours
>
> 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
prev parent reply other threads:[~2018-09-12 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15366609483983@kroah.com>
[not found] ` <1536660925253231@kroah.com>
[not found] ` <153666090117436@kroah.com>
[not found] ` <1536660870156224@kroah.com>
2018-09-12 15:36 ` Patch "tracing: Handle CC_FLAGS_FTRACE more accurately" has been added to the ...-stable tree Vasily Gorbik
2018-09-12 18:24 ` Greg KH [this message]
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=20180912182428.GA20855@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=gor@linux.ibm.com \
--cc=rostedt@goodmis.org \
--cc=stable-commits@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.