On Wed 2017-02-01 14:02:43, Josh Poimboeuf wrote:
> On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> > Here's v4, based on linux-next/master. Mostly minor changes this time,
> > primarily due to Petr's v3 comments.
>
> So far, the only review comments have been related to the fir
On Wed, 1 Feb 2017, Josh Poimboeuf wrote:
> If there are no more comments, it would be great to get these patches in
> for the 4.11 merge window. Any objections to that?
That'd mean that the exposure in -next would be really short, which I'd
like to avoid. I'd love to tentatively target 4.12 t
On Wed, 1 Feb 2017, Josh Poimboeuf wrote:
> On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> > Here's v4, based on linux-next/master. Mostly minor changes this time,
> > primarily due to Petr's v3 comments.
>
> So far, the only review comments have been related to the first patc
On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> Here's v4, based on linux-next/master. Mostly minor changes this time,
> primarily due to Petr's v3 comments.
So far, the only review comments have been related to the first patch,
of which I just posted an updated version.
If the
Here's v4, based on linux-next/master. Mostly minor changes this time,
primarily due to Petr's v3 comments.
v4:
- add warnings for "impossible" scenarios in __save_stack_trace_reliable()
- sort _TIF_ALLWORK_MASK flags
- move klp_transition_work to transition.c. This resulted in the following
