All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akinobu Mita <akinobu.mita@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: "Heitke, Kenneth" <kenneth.heitke@intel.com>,
	linux-nvme@lists.infradead.org, linux-pm@vger.kernel.org,
	Keith Busch <keith.busch@intel.com>,
	Sagi Grimberg <sagi@grimberg.me>, Jens Axboe <axboe@fb.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/2] nvme: add thermal zone infrastructure
Date: Sat, 18 May 2019 00:36:21 +0900	[thread overview]
Message-ID: <CAC5umyhu6_s_CTvOL4_Rp7unqcw+jt9fPo++iGnumqDFQJecxA@mail.gmail.com> (raw)
In-Reply-To: <20190517150924.GA25006@localhost.localdomain>

2019年5月18日(土) 0:14 Keith Busch <kbusch@kernel.org>:
>
> On Sat, May 18, 2019 at 12:01:57AM +0900, Akinobu Mita wrote:
> >
> > This is work_struct, not workqueue.  So it can't be destroyed.
> > But I noticed that we should call flush_work for thermal_work at
> > unregistering thermal zone devices.
>
> Instead of creating yet-another-work_struct, let's append this event's
> action to the existing async_event_work.

Good idea.

WARNING: multiple messages have this Message-ID (diff)
From: akinobu.mita@gmail.com (Akinobu Mita)
Subject: [PATCH 1/2] nvme: add thermal zone infrastructure
Date: Sat, 18 May 2019 00:36:21 +0900	[thread overview]
Message-ID: <CAC5umyhu6_s_CTvOL4_Rp7unqcw+jt9fPo++iGnumqDFQJecxA@mail.gmail.com> (raw)
In-Reply-To: <20190517150924.GA25006@localhost.localdomain>

2019?5?18?(?) 0:14 Keith Busch <kbusch at kernel.org>:
>
> On Sat, May 18, 2019@12:01:57AM +0900, Akinobu Mita wrote:
> >
> > This is work_struct, not workqueue.  So it can't be destroyed.
> > But I noticed that we should call flush_work for thermal_work at
> > unregistering thermal zone devices.
>
> Instead of creating yet-another-work_struct, let's append this event's
> action to the existing async_event_work.

Good idea.

  reply	other threads:[~2019-05-17 15:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 15:17 [PATCH 0/2] nvme: add thermal zone devices Akinobu Mita
2019-05-15 15:17 ` Akinobu Mita
2019-05-15 15:17 ` [PATCH 1/2] nvme: add thermal zone infrastructure Akinobu Mita
2019-05-15 15:17   ` Akinobu Mita
2019-05-15 19:15   ` Keith Busch
2019-05-15 19:15     ` Keith Busch
2019-05-16 15:22     ` Akinobu Mita
2019-05-16 15:22       ` Akinobu Mita
2019-05-16 15:26       ` Keith Busch
2019-05-16 15:26         ` Keith Busch
2019-05-16 14:23   ` Minwoo Im
2019-05-16 14:23     ` Minwoo Im
2019-05-16 14:32   ` Minwoo Im
2019-05-16 14:32     ` Minwoo Im
2019-05-16 16:17     ` Akinobu Mita
2019-05-16 16:17       ` Akinobu Mita
2019-05-16 16:48       ` Minwoo Im
2019-05-16 16:48         ` Minwoo Im
2019-05-16 14:35   ` Akinobu Mita
2019-05-16 14:35     ` Akinobu Mita
2019-05-16 21:22   ` Heitke, Kenneth
2019-05-16 21:22     ` Heitke, Kenneth
2019-05-17 15:01     ` Akinobu Mita
2019-05-17 15:01       ` Akinobu Mita
2019-05-17 15:09       ` Keith Busch
2019-05-17 15:09         ` Keith Busch
2019-05-17 15:36         ` Akinobu Mita [this message]
2019-05-17 15:36           ` Akinobu Mita
2019-05-16 21:25   ` Heitke, Kenneth
2019-05-16 21:25     ` Heitke, Kenneth
2019-05-17 15:03     ` Akinobu Mita
2019-05-17 15:03       ` Akinobu Mita
2019-05-16 23:44   ` Chaitanya Kulkarni
2019-05-16 23:44     ` Chaitanya Kulkarni
2019-05-17 15:35     ` Akinobu Mita
2019-05-17 15:35       ` Akinobu Mita
2019-05-15 15:17 ` [PATCH 2/2] nvme-pci: support thermal zone Akinobu Mita
2019-05-15 15:17   ` Akinobu Mita
2019-05-15 17:03   ` Keith Busch
2019-05-15 17:03     ` Keith Busch
2019-05-16 14:30     ` Akinobu Mita
2019-05-16 14:30       ` Akinobu Mita

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=CAC5umyhu6_s_CTvOL4_Rp7unqcw+jt9fPo++iGnumqDFQJecxA@mail.gmail.com \
    --to=akinobu.mita@gmail.com \
    --cc=axboe@fb.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=keith.busch@intel.com \
    --cc=kenneth.heitke@intel.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sagi@grimberg.me \
    /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.