From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755991AbcHBTKO (ORCPT <rfc822;w@1wt.eu>);
	Tue, 2 Aug 2016 15:10:14 -0400
Received: from mail-qk0-f172.google.com ([209.85.220.172]:32982 "EHLO
	mail-qk0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751824AbcHBTKG (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 2 Aug 2016 15:10:06 -0400
Date: Tue, 2 Aug 2016 15:02:44 -0400
From: Tejun Heo <tj@kernel.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: Michal Hocko <mhocko@kernel.org>, Geliang Tang <geliangtang@163.com>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
        "GeyslanG.Bem@Karyakshetra" <geyslan@gmail.com>,
        Masanari Iida <standby24x7@gmail.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Alan Stern <stern@rowland.harvard.edu>,
        Vlastimil Babka <vbabka@suse.cz>,
        Mel Gorman <mgorman@techsingularity.net>, linux-kernel@vger.kernel.org,
        linux-usb@vger.kernel.org, Saurabh Karajgaonkar <skarajga@visteon.com>
Subject: Re: [RFC] usb: host: u132-hcd: Remove deprecated
 create_singlethread_workqueue
Message-ID: <20160802190244.GH2542@mtj.duckdns.org>
References: <20160729131147.GJ2542@mtj.duckdns.org>
 <20160801135036.GH13544@dhcp22.suse.cz>
 <20160801142005.GB2542@mtj.duckdns.org>
 <1470125172.30985.4.camel@suse.com>
 <20160802081801.GC12403@dhcp22.suse.cz>
 <1470132203.30985.16.camel@suse.com>
 <20160802113409.GF12403@dhcp22.suse.cz>
 <1470138288.30985.18.camel@suse.com>
 <20160802124819.GM12403@dhcp22.suse.cz>
 <1470144588.30985.23.camel@suse.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1470144588.30985.23.camel@suse.com>
User-Agent: Mutt/1.6.2 (2016-07-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello,

On Tue, Aug 02, 2016 at 03:29:48PM +0200, Oliver Neukum wrote:
> Apparently if that is the requirement USB will have to define its own
> set of flags to use in such contexts. But still the calls as currently
> executed work. Taking away WQ_MEM_RECLAIM would create danger of
> introducing a regression. The issue with __GFP_DIRECT_RECLAIM already
> exists and can be fixed.

Alright, let's go with WQ_MEM_RECLAIM then.

Thanks.

-- 
tejun