All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
	mingo@redhat.com, will@kernel.org, apw@canonical.com,
	joe@perches.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] mutex: nuke mutex_trylock_recursive
Date: Tue, 16 Feb 2021 13:38:49 +0100	[thread overview]
Message-ID: <e8374454-4c2b-b718-a0fc-0e25662c3f44@gmail.com> (raw)
In-Reply-To: <YCuaup4u1ZE6crE0@hirez.programming.kicks-ass.net>



Am 16.02.21 um 11:13 schrieb Peter Zijlstra:
> On Tue, Feb 16, 2021 at 10:29:00AM +0100, Daniel Vetter wrote:
>> On Tue, Feb 16, 2021 at 09:21:46AM +0100, Christian König wrote:
>>> The last user went away in the 5.11 cycle.
>>>
>>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Nice.
>>
>> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> I think would be good to still stuff this into 5.12 before someone
>> resurrects this zombie.
> Already done:
>
>    https://lkml.kernel.org/r/161296556531.23325.10473355259841906876.tip-bot2@tip-bot2

One less bad concept to worry about.

But your patch is missing to remove the checkpatch.pl check for this :)

Cheers,
Christian.

WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
	mingo@redhat.com, will@kernel.org,  apw@canonical.com,
	joe@perches.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] mutex: nuke mutex_trylock_recursive
Date: Tue, 16 Feb 2021 13:38:49 +0100	[thread overview]
Message-ID: <e8374454-4c2b-b718-a0fc-0e25662c3f44@gmail.com> (raw)
In-Reply-To: <YCuaup4u1ZE6crE0@hirez.programming.kicks-ass.net>



Am 16.02.21 um 11:13 schrieb Peter Zijlstra:
> On Tue, Feb 16, 2021 at 10:29:00AM +0100, Daniel Vetter wrote:
>> On Tue, Feb 16, 2021 at 09:21:46AM +0100, Christian König wrote:
>>> The last user went away in the 5.11 cycle.
>>>
>>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Nice.
>>
>> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> I think would be good to still stuff this into 5.12 before someone
>> resurrects this zombie.
> Already done:
>
>    https://lkml.kernel.org/r/161296556531.23325.10473355259841906876.tip-bot2@tip-bot2

One less bad concept to worry about.

But your patch is missing to remove the checkpatch.pl check for this :)

Cheers,
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-02-16 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  8:21 [PATCH] mutex: nuke mutex_trylock_recursive Christian König
2021-02-16  8:21 ` Christian König
2021-02-16  9:29 ` Daniel Vetter
2021-02-16  9:29   ` Daniel Vetter
2021-02-16 10:13   ` Peter Zijlstra
2021-02-16 10:13     ` Peter Zijlstra
2021-02-16 12:38     ` Christian König [this message]
2021-02-16 12:38       ` Christian König
2021-02-16 12:44       ` Peter Zijlstra
2021-02-16 12:44         ` Peter Zijlstra

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=e8374454-4c2b-b718-a0fc-0e25662c3f44@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=apw@canonical.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@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.