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=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 30EBFC43381 for ; Wed, 17 Feb 2021 19:44:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1590E64E4B for ; Wed, 17 Feb 2021 19:44:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233784AbhBQToA (ORCPT ); Wed, 17 Feb 2021 14:44:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:58244 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233314AbhBQTnm (ORCPT ); Wed, 17 Feb 2021 14:43:42 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 9658464E45; Wed, 17 Feb 2021 19:43:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1613590981; bh=LlwTiP8/hl3yvWK78ty94eQWzvbMMEBmhJXYr7fFCGw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=LeXPpXW9sSFaAMYkPWATCI2c1AmR8XraBwEzu5gLRubwCcRT9TpTY5pdqFijlZ6cS sNYSONm5cxfkGtWN6CCBpsMNab/3Y9Jkkna3UoBYjbVUm6xU2OyKzHdkydxAE6G+Uu z7+jerCAAEivb+o496+evKQQTz3YGqqTAHvJtJkEtiS0IzVKfq8tNm5kdC1LgQRiIQ PsXfC+u33/sKbcm7fzUsnaWVWzJ/yYEhjahbNpE6EwUdjmXQM3dVHFemrJpGaSqfFV Gibb4YwNeyZStStpMRIIPS99PbQ+x7YjBmwAbjZ+hzRItz8MLJqCZiLoi9nitzKnjk hKBUCFah2uQSA== Received: by mail-ej1-f54.google.com with SMTP id f14so24334673ejc.8; Wed, 17 Feb 2021 11:43:01 -0800 (PST) X-Gm-Message-State: AOAM531s01eQyS4tnsrN+EU1SxiYMRuzy9973VLuoLnDuBkH2sFPGn2w 4zAhEDHpuE537cLPD6iEIC3Nm7o6vTGeq99POw== X-Google-Smtp-Source: ABdhPJzAMNa126EXLIevgRQHmZuiDRjOGeslDBdTqUCA1s4KD+K8imQWfogzr0YaUNopBqs64UbcpGOwQFT9y0JO5q8= X-Received: by 2002:a17:906:d1d0:: with SMTP id bs16mr553549ejb.468.1613590980184; Wed, 17 Feb 2021 11:43:00 -0800 (PST) MIME-Version: 1.0 References: <20210215224258.1231449-1-saravanak@google.com> In-Reply-To: <20210215224258.1231449-1-saravanak@google.com> From: Rob Herring Date: Wed, 17 Feb 2021 13:42:47 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] of: property: fw_devlink: Ignore interrupts property for some configs To: Saravana Kannan Cc: Frank Rowand , Linus Walleij , Greg Kroah-Hartman , Thierry Reding , Guenter Roeck , Android Kernel Team , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 15, 2021 at 4:43 PM Saravana Kannan wrote: > > When CONFIG_OF_IRQ is not defined, it doesn't make sense to parse > interrupts property. > > Also, parsing and tracking interrupts property breaks some PPC > devices[1]. But none of the IRQ drivers in PPC seem ready to be > converted to a proper platform (or any bus) driver. So, there's not much > of a point in tracking the interrupts property for CONFIG_PPC. So, let's > stop parsing interrupts for CONFIG_PPC. > > [1] - https://lore.kernel.org/lkml/20210213185422.GA195733@roeck-us.net/ > Fixes: 4104ca776ba3 ("of: property: Add fw_devlink support for interrupts") > Reported-by: Guenter Roeck > Signed-off-by: Saravana Kannan > --- > Greg/Rob, > > I believe this needs to land on driver-core-next. Acked-by: Rob Herring