From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E3592C2D0A8 for ; Wed, 23 Sep 2020 17:46:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9644820708 for ; Wed, 23 Sep 2020 17:46:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600883200; bh=wlAp8hRPzNUumB6gareqbwIrZtOY/IiDDRAA/oeRYTA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=n/GYtH/R8Klz5ldFUW/+nzENPyswpgcDRtJ+YOB+TSWiCoIM8PosMkth23J7m83ZG vw8BrL9TwUWvXnl7MtBrvZMDBxZIDduiNxZ7LlXmbeKagAsvqVVoqK8FpUWjt5ELmK Cwtrvv2P0pgu1HHDMVn53fkN2sM5Vo0SnaTscFEc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726632AbgIWRqk (ORCPT ); Wed, 23 Sep 2020 13:46:40 -0400 Received: from forward1-smtp.messagingengine.com ([66.111.4.223]:34797 "EHLO forward1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726130AbgIWRqj (ORCPT ); Wed, 23 Sep 2020 13:46:39 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 73CF01940517; Wed, 23 Sep 2020 13:46:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 23 Sep 2020 13:46:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=xgAZbC oQoNirkiRWp+iZJurkXrxYqX3CLo9LqvidP9A=; b=TKue7ip3GIo4YV9FrBetEW BRxLGqoqirYmM/gqFuarrMSQ1f9qbQJbLaYw3x1wdhnmfePoe8Q0cJve/kdooG4K TlFihg0Rn5ZTltlhhR/OVbv8gDR7fAKJI9HvQ4Wr8IYd+lOHmR4vBywgHKOyGtJ8 7qVFqnkQIpElYbl676bWCYRvAMcckYGGwrygIrbJ9A2KKk5mzNdUxjKfgqPH0P55 eKORilbGnjSPyvqH4XM4shcETgXLJkHFAxzXCRVXvKtRGiN0UqWNt406YUvpz7/n iJKyeq1QkvLVs7i4tHT7l3zGzGucEMX5Q85E+RloO417gLTQgX2LU15IZ8CZxk3g == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeigdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgmffjsehlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgqeenucggtf frrghtthgvrhhnpeetvdelgeffgfdutdelvddvtdetffejtefgveevueeggfellefhveev feduueduvdenucfkphepkeefrdekiedrjeegrdeigeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) by mail.messagingengine.com (Postfix) with ESMTPA id EC256306467E; Wed, 23 Sep 2020 13:46:37 -0400 (EDT) Date: Wed, 23 Sep 2020 19:46:57 +0200 From: Greg KH To: Oliver Neukum Cc: himadrispandya@gmail.com, stern@rowland.harvard.edu, linux-usb@vger.kernel.org Subject: Re: [RFC] change the new message to provide for memory allocations Message-ID: <20200923174657.GA104361@kroah.com> References: <20200923134348.23862-1-oneukum@suse.com> <20200923172103.GC3732240@kroah.com> <1600882331.29329.0.camel@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1600882331.29329.0.camel@suse.com> Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Wed, Sep 23, 2020 at 07:32:11PM +0200, Oliver Neukum wrote: > Am Mittwoch, den 23.09.2020, 19:21 +0200 schrieb Greg KH: > > On Wed, Sep 23, 2020 at 03:43:34PM +0200, Oliver Neukum wrote: > > > Control messages have to work in situtaions where you need to > > > use GFP_NOIO. Hence wrappers for them that allocate memory must have > > > an API that allows for that. > > > > > > Signed-off-by: Oliver Neukum > > > > > > > So you unwind my mess and then fix it back up, nice, no objections from > > me, thanks for doing this. > > > > You sent this as "RFC", but it seems sane, want me to take this as-is or > > do you want to wait to send a "real" set of patches? > > Hi, > > this is a fairly fundamental API. If we overlooked something the first > time I would hate to see it happen twice. Are you in a hurry? No, I just don't want to see more people build on this as-is :)