mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>, <daniel@ffwll.ch>
Cc: <maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
	<tzimmermann@suse.de>, <airlied@gmail.com>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm: Add DRM-managed alloc_workqueue() and alloc_ordered_workqueue()
Date: Tue, 14 Nov 2023 09:03:04 -0700	[thread overview]
Message-ID: <e5ce0994-6698-3ade-4553-76d456fe9110@quicinc.com> (raw)
In-Reply-To: <20230118032413.6496-1-jiasheng@iscas.ac.cn>

On 1/17/2023 8:24 PM, Jiasheng Jiang wrote:
>> On Tue, Jan 10, 2023 at 11:24:47PM +0800, Jiasheng Jiang wrote:
>>> Add drmm_alloc_workqueue() and drmm_alloc_ordered_workqueue(), the helpers
>>> that provide managed workqueue cleanup. The workqueue will be destroyed
>>> with the final reference of the DRM device.
>>>
>>> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
>>
>> Yeah I think this looks nice.
>>
>> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> I'm assuming driver maintainers will pick this up, if not please holler.
>>
>> Also the threading seems broken, it's not a patch series. The b4 tool or
>> git send-email (of all the patches of the entire series at once, not each
>> individually) should get this right.
>>
>> Unfortunately I did't find the right link in the kernel docs, or at least
>> they're not as detailed as I hoped.
>>
>> Also your previous submission had iirc a bunch more patches, do you plan
>> to include them all in the next patch set?
> 
> I have found that some previous patches have already been applied.
> Need I just convert alloc*workqueue into drmm_alloc*workqueue and remove
> the destroy_workqueue?
> Or need I convert all the alloc*workqueue in the DRM?
> 
> Thanks,
> Jiang

Unless I'm missing something, I don't see that this ever got applied.  I 
have a use for this interface in the qaic driver.

Jiang, are you planning on posting a v2?

-Jeff

  reply	other threads:[~2023-11-14 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  3:24 Jiasheng Jiang
2023-11-14 16:03 ` Jeffrey Hugo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10 15:24 Jiasheng Jiang
2023-01-11 22:46 ` Daniel Vetter

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=e5ce0994-6698-3ade-4553-76d456fe9110@quicinc.com \
    --to=quic_jhugo@quicinc.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jiasheng@iscas.ac.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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®