mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
	Andrey Grodzovsky <andrey.grodzovsky@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	amd-gfx@lists.freedesktop.org, Christian.Koenig@amd.com
Subject: Re: [PATCH] Revert "workqueue: remove unused cancel_work()"
Date: Thu, 19 May 2022 21:52:10 -1000	[thread overview]
Message-ID: <YodIquufXzK581gw@slm.duckdns.org> (raw)
In-Reply-To: <045157bb-31a0-2d76-18b7-4272fab218ef@gmail.com>

On Fri, May 20, 2022 at 08:22:39AM +0200, Christian König wrote:
> Am 20.05.22 um 02:47 schrieb Lai Jiangshan:
> > On Thu, May 19, 2022 at 11:04 PM Andrey Grodzovsky
> > <andrey.grodzovsky@amd.com> wrote:
> > > See this patch-set https://www.spinics.net/lists/amd-gfx/msg78514.html, specifically patch
> > > 'drm/amdgpu: Switch to delayed work from work_struct.
> > > 
> > > I will just reiterate here -
> > > 
> > > We need to be able to do non blocking cancel pending reset works
> > > from within GPU reset. Currently kernel API allows this only
> > > for delayed_work and not for work_struct.
> > > 
> > I'm OK with the change.
> > 
> > With an updated changelog:
> > 
> > Reviewed-by: Lai Jiangshan<jiangshanlai@gmail.com>
> 
> Good morning guys,
> 
> for the patch itself Reviewed-by: Christian König <christian.koenig@amd.com>
> 
> And just for the record: We plan to push this upstream through the drm
> branches, if anybody has any objections to that please speak up.

Andrey, care to resend with updated description?

Thanks.

-- 
tejun

  reply	other threads:[~2022-05-20  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 13:56 Andrey Grodzovsky
2022-05-19 14:52 ` Lai Jiangshan
     [not found]   ` <e1e2e63d-a1a9-12ad-97a7-a3771210edda@amd.com>
2022-05-20  0:47     ` Lai Jiangshan
2022-05-20  6:22       ` Christian König
2022-05-20  7:52         ` Tejun Heo [this message]
2022-05-21  4:04           ` Andrey Grodzovsky
2022-06-07 17:14             ` Tejun Heo
2022-06-07 17:39               ` Alex Deucher
2022-06-07 19:25                 ` Tejun Heo

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=YodIquufXzK581gw@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=Christian.Koenig@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrey.grodzovsky@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®