Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp772885iog; Wed, 29 Jun 2022 09:53:14 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tg2FR7R7zo0rTHjW/zwnratZngSqIvFM9nxTnsSwwnrlAHg+NQc9fnGXHhE+avx9uVTnAF X-Received: by 2002:a17:90a:408f:b0:1e3:23a:2370 with SMTP id l15-20020a17090a408f00b001e3023a2370mr4826844pjg.84.1656521594165; Wed, 29 Jun 2022 09:53:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656521594; cv=none; d=google.com; s=arc-20160816; b=Sw/mWuViSK0LZ7M/NVY4ZMiDfSh9PTU9dGWFGeqPSGLqz9h1pXoG+DBsxxkZbwyo80 CfHWdDfHi5pbFuNbCwFyC43hynTsYWQzJOlS92efZMjPOxV9j0psEQcDdHdRirp526+R ecofZcNa9DgoiSWzzYvzCrBhr1kymJRxz0l4St2d0pSA1Ep9gcCAmDRKLWnLYC6a90wD 1VSahNMDoZQffAZ/rrECZ1WOJtYvxoqE2Uh5nN6VBN9XLjloRdTMM6UrtZK5ZfFi6BE6 yTAtOn3BuKyozuNyEEM6fxyvUgWFhSK0wOEgP22LXKEe4j02GrJzFeckQ4zYwzEdLEzF NYmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=oqsTdiLfWpJvLwXGqGd7Je96p2+qJUVXjf/cM3xQGqA=; b=GY7A+sVb2erdsyGGOBJ/DVq5D7/YMIIpZKXov70Sqllo6fpT9z9ZSGFYI2ZorS0cuf djv7CGK8G1IozG1aOWPYn2VOv+9RZzQ3MJikRngGdZ/dPT2ZIl5jQOc5LT1gaJqHbDpg Z7zE8Htq+wFkPmYKu16Tm4gUeMYJOK/6Sv61TIabVv05h9SbEegeiJlOXsiIbQrK65er pqDrUD9YIEKs2BjKpDnuowCgfhiyp+k7xc2NfzzO4fxur5GXVpa38UbG465C9fXSbXCN /cfvuyVdt02x9c6+rrDOlOlPx/bgbuJJxZdpPQSVEeFfe0CZj2B7HAhCTCarlbHQdOjH c+PA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=ZNKx75q7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n15-20020a65488f000000b0040c583c37eesi24420280pgs.601.2022.06.29.09.53.00; Wed, 29 Jun 2022 09:53:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=ZNKx75q7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229982AbiF2Qi0 (ORCPT + 99 others); Wed, 29 Jun 2022 12:38:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49078 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbiF2QiX (ORCPT ); Wed, 29 Jun 2022 12:38:23 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E9EAA1A064; Wed, 29 Jun 2022 09:38:21 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 827E861CEB; Wed, 29 Jun 2022 16:38:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 38917C34114; Wed, 29 Jun 2022 16:38:18 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="ZNKx75q7" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1656520696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oqsTdiLfWpJvLwXGqGd7Je96p2+qJUVXjf/cM3xQGqA=; b=ZNKx75q7yT64VSkCyZYIG/UKOvmj2k2d+g2rhHqSjeu1Zdq/d9bl9TVbzbqjHVmavQYjof KuXqFM7kkX42Se1F8LiCZUWNnALfjzJmU8Ysdci7RZK9kyZOyLEcxbiTpNjTBsI4Ywyan1 UosUpF3Ud0xyjAhkSthaJ/NO4xyrkkI= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 2422f02d (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 29 Jun 2022 16:38:16 +0000 (UTC) Date: Wed, 29 Jun 2022 18:38:09 +0200 From: "Jason A. Donenfeld" To: Christoph Hellwig Cc: Greg Kroah-Hartman , Arve =?utf-8?B?SGrDuG5uZXbDpWc=?= , Todd Kjos , Martijn Coenen , Joel Fernandes , Christian Brauner , Hridya Valsaraju , Suren Baghdasaryan , Theodore Ts'o , "David S. Miller" , Eric Dumazet , Jakub Kicinski , "Alex Xu (Hello71)" , Paolo Abeni , Rob Herring , "Paul E. McKenney" , Frederic Weisbecker , Neeraj Upadhyay , Josh Triplett , Steven Rostedt , Mathieu Desnoyers , Lai Jiangshan , Shuah Khan , linux-kernel@vger.kernel.org, wireguard@lists.zx2c4.com, netdev@vger.kernel.org, rcu@vger.kernel.org, linux-kselftest@vger.kernel.org Subject: Re: [PATCH] remove CONFIG_ANDROID Message-ID: References: <20220629150102.1582425-1-hch@lst.de> <20220629150102.1582425-2-hch@lst.de> <20220629161020.GA24891@lst.de> <20220629161527.GA24978@lst.de> <20220629163007.GA25279@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220629163007.GA25279@lst.de> X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 29, 2022 at 06:30:07PM +0200, Christoph Hellwig wrote: > On Wed, Jun 29, 2022 at 06:25:32PM +0200, Jason A. Donenfeld wrote: > > Anyway, instead of the slow drip of "facts" and ≤three sentence emails, > > can you just write up a paragraph that indicates this is safe to do (for > > both (1) and (2)) in your v+1? > > Why would I care? If your config wakeups up so often that you need > special casing find a way to deal with it. You should care, because the change you're suggesting might break code that I maintain. If you don't care about breaking my code with your change, than just have my "nack", and it'll be up to Greg to decide whether he wants to apply this despite the nack for two separate affected code spots. On the technical topic, an Android developer friend following this thread just pointed out to me that Android doesn't use PM_AUTOSLEEP and just has userspace causing suspend frequently. So by his rough estimation your patch actually *will* break Android devices. Zoinks. Maybe he's right, maybe he's not -- I don't know -- but you should probably look into this if you want this patch to land without breakage. Jason