On Sat, Nov 24, 2018 at 01:46:34PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 15:00:11 -0500
Sasha Levin wrote:
What will happen with these is that once Greg's scripts process Linus's
tree he'll end up with this patch series inconsistently backported to
stable trees, which is not what
On Sat, Nov 24, 2018 at 01:46:34PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 15:00:11 -0500
Sasha Levin wrote:
What will happen with these is that once Greg's scripts process Linus's
tree he'll end up with this patch series inconsistently backported to
stable trees, which is not what
On Fri, 23 Nov 2018 15:00:11 -0500
Sasha Levin wrote:
> On Fri, Nov 23, 2018 at 02:26:17PM -0500, Steven Rostedt wrote:
> >On Fri, 23 Nov 2018 13:34:15 -0500
> >Sasha Levin wrote:
> >
> >> Does this mean that someone (Steve) will send a backport of this to all
> >> relevant stable trees?
On Fri, 23 Nov 2018 15:00:11 -0500
Sasha Levin wrote:
> On Fri, Nov 23, 2018 at 02:26:17PM -0500, Steven Rostedt wrote:
> >On Fri, 23 Nov 2018 13:34:15 -0500
> >Sasha Levin wrote:
> >
> >> Does this mean that someone (Steve) will send a backport of this to all
> >> relevant stable trees?
On Fri, Nov 23, 2018 at 02:26:17PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 13:34:15 -0500
Sasha Levin wrote:
Does this mean that someone (Steve) will send a backport of this to all
relevant stable trees? Right now it looks like the series will randomly
apply on a mix of trees, which
On Fri, Nov 23, 2018 at 02:26:17PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 13:34:15 -0500
Sasha Levin wrote:
Does this mean that someone (Steve) will send a backport of this to all
relevant stable trees? Right now it looks like the series will randomly
apply on a mix of trees, which
On Fri, 23 Nov 2018 13:34:15 -0500
Sasha Levin wrote:
> Does this mean that someone (Steve) will send a backport of this to all
> relevant stable trees? Right now it looks like the series will randomly
> apply on a mix of trees, which can't be good.
Nope. I stated that in my 0 patch.
-- Steve
On Fri, 23 Nov 2018 13:34:15 -0500
Sasha Levin wrote:
> Does this mean that someone (Steve) will send a backport of this to all
> relevant stable trees? Right now it looks like the series will randomly
> apply on a mix of trees, which can't be good.
Nope. I stated that in my 0 patch.
-- Steve
On Fri, Nov 23, 2018 at 12:12:53PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 10:06:05 +0100
Helge Deller wrote:
> How should we proceed with this patch?
My suggestion, although I didn't looked too much on it:
Apply it to v4.9 and higher only.
I think I started fixing trace
On Fri, Nov 23, 2018 at 12:12:53PM -0500, Steven Rostedt wrote:
On Fri, 23 Nov 2018 10:06:05 +0100
Helge Deller wrote:
> How should we proceed with this patch?
My suggestion, although I didn't looked too much on it:
Apply it to v4.9 and higher only.
I think I started fixing trace
On Fri, 23 Nov 2018 10:06:05 +0100
Helge Deller wrote:
> > How should we proceed with this patch?
>
> My suggestion, although I didn't looked too much on it:
> Apply it to v4.9 and higher only.
> I think I started fixing trace functionality on parisc around 4.6,
> which is probably why
On Fri, 23 Nov 2018 10:06:05 +0100
Helge Deller wrote:
> > How should we proceed with this patch?
>
> My suggestion, although I didn't looked too much on it:
> Apply it to v4.9 and higher only.
> I think I started fixing trace functionality on parisc around 4.6,
> which is probably why
HI Sasha,
On 23.11.18 08:30, Sasha Levin wrote:
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 03274a3ffb44 tracing/fgraph: Adjust fgraph depth before calling
trace return callback.
The bot has tested the following trees: v4.19.3, v4.14.82, v4.9.138,
HI Sasha,
On 23.11.18 08:30, Sasha Levin wrote:
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 03274a3ffb44 tracing/fgraph: Adjust fgraph depth before calling
trace return callback.
The bot has tested the following trees: v4.19.3, v4.14.82, v4.9.138,
From: "Steven Rostedt (VMware)"
The function_graph_entry() function does the work of calling the function
graph hook function and the management of the shadow stack, simplifying the
work done in the architecture dependent prepare_ftrace_return().
Have parisc use the new code, and remove the
From: "Steven Rostedt (VMware)"
The function_graph_entry() function does the work of calling the function
graph hook function and the management of the shadow stack, simplifying the
work done in the architecture dependent prepare_ftrace_return().
Have parisc use the new code, and remove the
16 matches
Mail list logo
