All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Subject: Re: [PATCH v2.6.36-rc7 2/2] shpchp: update workqueue usage
Date: Fri, 15 Oct 2010 22:08:24 +0200	[thread overview]
Message-ID: <4CB8B4B8.8090501@kernel.org> (raw)
In-Reply-To: <20101015125257.73e8d8df@jbarnes-desktop>

Hello,

On 10/15/2010 09:52 PM, Jesse Barnes wrote:
>> * Rename shpchp_wq to shpchp_ordered_wq and add non-ordered shpchp_wq
>>   which is used instead of the system workqueue.  This is to remove
>>   the use of flush_scheduled_work() which is deprecated and scheduled
>>   for removal.
>>
>> * With cmwq in place, there's no point in creating workqueues lazily.
>>   Create both shpchp_wq and shpchp_ordered_wq upfront.
>>
>> * Include workqueue.h from shpchp.h.
> 
> Applied these two, thanks.  I think Kenji-san will probably let me know
> if pciehp suddenly breaks as a result. :)

Just in case, these are in no way aimed for v2.6.36.  They are at the
earliest for v2.6.37-rc1.  Thanks a lot.

-- 
tejun

  reply	other threads:[~2010-10-15 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 14:47 [PATCH v2.6.36-rc7 1/2] pciehp: update workqueue usage Tejun Heo
2010-10-15 14:47 ` [PATCH v2.6.36-rc7 2/2] shpchp: " Tejun Heo
2010-10-15 19:52   ` Jesse Barnes
2010-10-15 20:08     ` Tejun Heo [this message]
2010-10-15 20:17       ` Jesse Barnes
2010-10-15 21:25     ` Kenji Kaneshige
2010-10-18  3:03   ` Jesse Barnes
2010-10-18  5:02     ` Tejun Heo
2010-10-18  6:34       ` 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=4CB8B4B8.8090501@kernel.org \
    --to=tj@kernel.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 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.