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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 72755C433F5 for ; Fri, 30 Sep 2022 17:55:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231251AbiI3RzY (ORCPT ); Fri, 30 Sep 2022 13:55:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57316 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231192AbiI3RzW (ORCPT ); Fri, 30 Sep 2022 13:55:22 -0400 Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6B7BF79EEA; Fri, 30 Sep 2022 10:55:21 -0700 (PDT) Received: by mail-pl1-x62e.google.com with SMTP id c24so4606934plo.3; Fri, 30 Sep 2022 10:55:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date; bh=oIAo9+qWUeQbXeHzAy+ugcYbG6Lm0wKQlqadtQ8eNSA=; b=L/Jm/QyNeAQsX6+TeyY0u4/7zeV88gIhYmLe2m73zwA0wA/SJwDkIfQXSSbCUMvZRM acULk+m2YNyYFhFx8tcXL6TehWZL/D3wdG2g4SSdVTCUIx4mfudsC1OuSGTXYaA9ksyL gXs5jQYipA18IFaU8v8eLJzatgtz6IqMQ2URxp04w4EapLyNuLhDJPCMsJcqUP79I8yk Jc8Rl3Dp1j4sSwMz5ayOWj6t02lnmMne66MkBzg5grVaslbsFA9U/+el0e5csEXQYfxN tRKuOTDQHGlsdNnUNuPVMrMXTZy6pqgEq0VWyDP5muDgaWbQkvBJQDzD8qkQqcKxTmY9 BShw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=oIAo9+qWUeQbXeHzAy+ugcYbG6Lm0wKQlqadtQ8eNSA=; b=5KYdup0giLKXNBgzKDcIRHj0WhaPRzdptPf4bD2Qic2Jb5lwi6KOOpFQsriEWzS3ZN lDEB5FZ7bhP9VsJ0HmzTUJ7A+h80izp5/Bzf+OIU9/fOXnrqa7inUy7BVsmv2lOAq5AA t6MAO/7bbSoTgRte6MqIZ9V0DQKhFQEHtxk8chZV6AUO+p3e9uYl6BwKMuqN/pwA/Sse PAfdo9Gtx1swFNdHNeo1SeWpI+F0HFzMQ/uFO3wsKL3G2loXmtdHV8+9kK23o383qv7U OZBudGMdb0se8vCAkTQUmtfH5KoVPpmsP/jiFuJMC/Hsb7OnkdScz/NReszxV8H4DpCS 8WNQ== X-Gm-Message-State: ACrzQf0Q/lnVYR75x9H7532HcbfxnRIsW0UHSgbPa7cCh4cOhp8+t0Pf OeoJ6/g20h88J/GV2f1QqsQ= X-Google-Smtp-Source: AMsMyM52dJzRPZQA4CrgFqXqnB8JDUSQFWJSxghPXouTP3w78MpcSmkjO5+lWVlBP2dTfjQfG+s+sA== X-Received: by 2002:a17:90a:10d6:b0:20a:46a7:beb9 with SMTP id b22-20020a17090a10d600b0020a46a7beb9mr3505094pje.49.1664560520691; Fri, 30 Sep 2022 10:55:20 -0700 (PDT) Received: from google.com ([2620:15c:9d:2:d016:f5be:4ff2:43f]) by smtp.gmail.com with ESMTPSA id z17-20020aa79491000000b0053ebafa7c42sm2110574pfk.79.2022.09.30.10.55.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 30 Sep 2022 10:55:19 -0700 (PDT) Date: Fri, 30 Sep 2022 10:55:16 -0700 From: Dmitry Torokhov To: Andy Shevchenko Cc: "Rafael J. Wysocki" , Raul Rangel , ACPI Devel Maling List , linux-input , Hans de Goede , Mika Westerberg , Mario Limonciello , Tim Van Patten , Linus Walleij , "jingle.wu" , Dan Williams , Greg Kroah-Hartman , Jonathan Cameron , Len Brown , Nathan Chancellor , Nick Desaulniers , Terry Bowman , Tom Rix , Linux Kernel Mailing List , llvm@lists.linux.dev Subject: Re: [PATCH v6 06/13] ACPI: resources: Add wake_capable parameter to acpi_dev_irq_flags Message-ID: References: <20220929161917.2348231-1-rrangel@chromium.org> <20220929093200.v6.6.I8092e417a8152475d13d8d638eb4c5d8ea12ac7b@changeid> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Fri, Sep 30, 2022 at 08:42:13PM +0300, Andy Shevchenko wrote: > On Fri, Sep 30, 2022 at 07:13:37PM +0200, Rafael J. Wysocki wrote: > > On Fri, Sep 30, 2022 at 1:22 AM Dmitry Torokhov > > wrote: > > ... > > > I think that patches [5-8/13] from this series are significant > > framework changes, so it would make sense to route them via the ACPI > > tree. > > > > If this is fine with everybody, I will queue them up for merging into > > 6.1 (probably in the second half of the upcoming merge window). > > I believe it's fine from GPIO ACPI perspective (there shouldn't be conflict, > but if you wish you always may take this PR [1] to your tree (it's already in > GPIO tree pending v6.1), it may be considered as immutable tag. > > [1]: https://lore.kernel.org/linux-gpio/Yym%2Fj+Y9MBOIhWtK@black.fi.intel.com/ Yeah, having an immutable branch hanging off 6.0-rcN would be awesome - I could pull it and this would avoid any potential conflicts later. Thanks. -- Dmitry