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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 389D1C433FF for ; Mon, 29 Jul 2019 21:03:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 081CF2067D for ; Mon, 29 Jul 2019 21:03:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="h0yQPRrj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729780AbfG2VDy (ORCPT ); Mon, 29 Jul 2019 17:03:54 -0400 Received: from mail-lf1-f66.google.com ([209.85.167.66]:39023 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725894AbfG2VDx (ORCPT ); Mon, 29 Jul 2019 17:03:53 -0400 Received: by mail-lf1-f66.google.com with SMTP id v85so43025016lfa.6 for ; Mon, 29 Jul 2019 14:03:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SLwaZEH25wNqGZTB2HC+4XfUpsEwrKsTiwJGEkrXZM0=; b=h0yQPRrjNKlXGfFBoWoylITmjbz4SK0JegbN37szOKfhSVCcgDFpmM6/f4t2Mu9tMG ZWd1EFVeGSDBJhC5biZ3ZtwATb2l99NNxnlGXA9y2m7IcmKrIXcPQs0AB2aVeLDcxgIp zH57jcOguVqz4e5oNCbnoYI9t15QxN/XOs5TE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SLwaZEH25wNqGZTB2HC+4XfUpsEwrKsTiwJGEkrXZM0=; b=lGNGfDySPM1pqhFsHca4rJBa4VPQ6VbCKSSMTaSWPRVlSGIsMcNSLgJ1nqsVvkRfj3 J8xWRvd+/bOPI5YF+HoP2G7DNUdler40cAzdvhN3NTOkH9HdNe5GrQF4jddSGLzJlXlE FBWSrDXj7128/b6ozjNqawPB+rbNBnpWteyO8pZnrhcl6GFoB1nD849LWqTiST9Qw7Wr wz+WxDu+xQT6q1BMGTrbrA/iKrvuwmDot5qOQZvck3qHrKpYddk36aXQ6QvQMJcaXKSr 5BPItxMOCkJ/QGD7qEKWdYIGlAvup9vxdS3MPeU5hRg8ECOKvcG8g2yN61JMPy/Bt3Ks hNjg== X-Gm-Message-State: APjAAAXbwSMB3weBLNc/LP8xpKqlDqnr8I+xVvzbMzFFETRU2EL63REd v4AOMekXBxQLUn6KmshyBQ5EseFqPng= X-Google-Smtp-Source: APXvYqxRzrPR42dVEVvHlGWbNVW5dcWcpXgIbQB9cralb+rIzJBz0UqxqvKYtnou86RlViVFNuSWwg== X-Received: by 2002:ac2:4565:: with SMTP id k5mr52884544lfm.170.1564434231436; Mon, 29 Jul 2019 14:03:51 -0700 (PDT) Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com. [209.85.208.181]) by smtp.gmail.com with ESMTPSA id x22sm10989104lfq.20.2019.07.29.14.03.47 for (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jul 2019 14:03:49 -0700 (PDT) Received: by mail-lj1-f181.google.com with SMTP id m23so59880345lje.12 for ; Mon, 29 Jul 2019 14:03:47 -0700 (PDT) X-Received: by 2002:a2e:80d6:: with SMTP id r22mr31685480ljg.83.1564434227544; Mon, 29 Jul 2019 14:03:47 -0700 (PDT) MIME-Version: 1.0 References: <20190729204954.25510-1-briannorris@chromium.org> <20190729205452.GA22785@archlinux-threadripper> In-Reply-To: <20190729205452.GA22785@archlinux-threadripper> From: Brian Norris Date: Mon, 29 Jul 2019 14:03:35 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] driver core: platform: return -ENXIO for missing GpioInt To: Nathan Chancellor Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Linux Kernel , Andy Shevchenko , Salvatore Bellizzi , Andy Shevchenko , Dmitry Torokhov , Enrico Granata , Enrico Granata , Enric Balletbo i Serra , Gwendal Grignou , ACPI Devel Maling List , Benson Leung , stable Content-Type: text/plain; charset="UTF-8" Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Mon, Jul 29, 2019 at 1:54 PM Nathan Chancellor wrote: > On Mon, Jul 29, 2019 at 01:49:54PM -0700, Brian Norris wrote: > > Side note: it might have helped alleviate some of this pain if there > > were email notifications to the mailing list when a patch gets applied. > > I didn't realize (and I'm not sure if Enrico did) that v2 was already > > merged by the time I noted its mistakes. If I had known, I would have > > suggested a follow-up patch, not a v3. > > I've found this to be fairly reliable for getting notified when > something gets applied if it is a tree that shows up in -next. > > https://www.kernel.org/get-notifications-for-your-patches.html I didn't send the original patch. I was only debugging/reviewing someone else's patch, and jumped in after its authorship (as it hit issues in our own CI system). So it was more of a "drive-by" scenario, and it doesn't sound like that page addresses this situation. Brian