[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877d6twh4n.fsf@email.froward.int.ebiederm.org>
Date: Tue, 10 May 2022 10:18:32 -0500
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
rjw@...ysocki.net, mingo@...nel.org, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, mgorman@...e.de,
Will Deacon <will@...nel.org>, tj@...nel.org,
linux-pm@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>,
Richard Weinberger <richard@....at>,
Anton Ivanov <anton.ivanov@...bridgegreys.com>,
Johannes Berg <johannes@...solutions.net>,
linux-um@...ts.infradead.org, Chris Zankel <chris@...kel.net>,
Max Filippov <jcmvbkbc@...il.com>,
linux-xtensa@...ux-xtensa.org, Jann Horn <jannh@...gle.com>,
Kees Cook <keescook@...omium.org>, linux-ia64@...r.kernel.org
Subject: Re: [PATCH v4 0/12] ptrace: cleaning up ptrace_stop
Sebastian Andrzej Siewior <bigeasy@...utronix.de> writes:
> On 2022-05-10 09:26:36 [-0500], Eric W. Biederman wrote:
>> Does anyone else have any comments on this patchset?
>>
>> If not I am going to apply this to a branch and get it into linux-next.
>
> Looks good I guess.
> Be aware that there will be clash due to
> https://lore.kernel.org/all/1649240981-11024-3-git-send-email-yangtiezhu@loongson.cn/
>
> which sits currently in -akpm.
Thanks for the heads up. That looks like the best kind of conflict.
One where code just disappears.
Eric
Powered by blists - more mailing lists