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=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 BAF57C43141 for ; Tue, 3 Dec 2019 19:19:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8C155214AF for ; Tue, 3 Dec 2019 19:19:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575400756; bh=Bf1TGgT+hkTT+k99zlKZwnqpp8q3VkvdLcp109SebHU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=bV1xU32eqDjOfC5/nP7yUTimp0xfmPUazIieJS5o3qbGjAn3huE0U0Crq1VpWgCqP BWZMaRUTALR2koZDqxvULbjGkr/7TxV0WGr/fmR5OKgCR+JaFB48AGyjlYGxk2npcr 4gidRdw/75MgQM4/PoD/vdGchylfTrCbh4ML+tLc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727438AbfLCTTP (ORCPT ); Tue, 3 Dec 2019 14:19:15 -0500 Received: from mail-oi1-f194.google.com ([209.85.167.194]:35828 "EHLO mail-oi1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727411AbfLCTTP (ORCPT ); Tue, 3 Dec 2019 14:19:15 -0500 Received: by mail-oi1-f194.google.com with SMTP id k196so4429574oib.2; Tue, 03 Dec 2019 11:19:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=VhGuCOSgKbP4988nwTLXWSOEoYXbGs7dSJ2jvNBuhT4=; b=gFrPoz3RmIy0EbzRdL0hnjFQ9UL/00ObT7O9bi3dwtJFEOu2y3DwZ7FvqqMG+aV7jP 6VF2QposcD/tp6/1GKcHxu1THC5wnQdGCwp1tk1WtkQCpgk62SboBFt+IKoiZpAFF9Q2 ePl+57KVzUUDRV4jSjsn+aGDShR5qUfb1PC4uHGe0rzuvkkU5Kdc+I4eJ+UuOThujjSX +oBMVuCQdFiSsLagik6m59YAXpD1GSGzru6/DiZA24HH35mWadmbVqCkexycazznETzx I7LEycLDsVyVOAdLwwM6nng6d52HWvNCHjljFGB4WRyMRqsUciNwgWwUxo3vB6GPUXpZ /QDw== X-Gm-Message-State: APjAAAV1XynyQXZ0JqtNWQmG5doANztH5dK1earvFeMSJ6V2+6C6V/Yp zTlHhPP2hsNk/aftdFz1tw== X-Google-Smtp-Source: APXvYqwXMVbFZmRe8QxF27h0Kfw3uND3v8OqThcJ1mrg8to0o6bWBoF0eqOAN8t4mfWgef6ZruT5hA== X-Received: by 2002:a05:6808:b2d:: with SMTP id t13mr5046037oij.83.1575400754268; Tue, 03 Dec 2019 11:19:14 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id y16sm1345750otq.60.2019.12.03.11.19.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Dec 2019 11:19:13 -0800 (PST) Date: Tue, 3 Dec 2019 13:19:13 -0600 From: Rob Herring To: Srinath Mannam Cc: Lorenzo Pieralisi , Bjorn Helgaas , Florian Fainelli , Ray Jui , Mark Rutland , Andy Shevchenko , Arnd Bergmann , bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Ray Jui , Srinath Mannam Subject: Re: [PATCH v3 1/6] dt-bindings: pci: Update iProc PCI binding for INTx support Message-ID: <20191203191913.GA20024@bogus> References: <1575349026-8743-1-git-send-email-srinath.mannam@broadcom.com> <1575349026-8743-2-git-send-email-srinath.mannam@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1575349026-8743-2-git-send-email-srinath.mannam@broadcom.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 3 Dec 2019 10:27:01 +0530, Srinath Mannam wrote: > From: Ray Jui > > Update the iProc PCIe binding document for better modeling of the legacy > interrupt (INTx) support > > Signed-off-by: Ray Jui > Signed-off-by: Srinath Mannam > --- > .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 48 ++++++++++++++++++---- > 1 file changed, 41 insertions(+), 7 deletions(-) > Please add Acked-by/Reviewed-by tags when posting new versions. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for acks received on the version they apply. If a tag was not added on purpose, please state why and what changed.