devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Leonardo Bras <leobras.c@gmail.com>
Cc: aik@ozlabs.ru, Frank Rowand <frowand.list@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] of/pci: Add IORESOURCE_MEM_64 to resource flags for 64-bit memory addresses
Date: Wed, 21 Apr 2021 07:51:57 -0500	[thread overview]
Message-ID: <20210421125157.GA967343@robh.at.kernel.org> (raw)
In-Reply-To: <20210415180050.373791-1-leobras.c@gmail.com>

On Thu, 15 Apr 2021 15:00:51 -0300, Leonardo Bras wrote:
> Many other resource flag parsers already add this flag when the input
> has bits 24 & 25 set, so update this one to do the same.
> 
> Some devices (like virtio-net) have more than one memory resource
> (like MMIO32 and MMIO64) and without this flag it would be needed to
> verify the address range to know which one is which.
> 
> Signed-off-by: Leonardo Bras <leobras.c@gmail.com>
> ---
>  drivers/of/address.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 

Applied, thanks!

      parent reply	other threads:[~2021-04-21 12:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 18:00 [PATCH 1/1] of/pci: Add IORESOURCE_MEM_64 to resource flags for 64-bit memory addresses Leonardo Bras
2021-04-15 18:59 ` Rob Herring
2021-04-16 20:57   ` Leonardo Bras
2021-04-19 15:44     ` Rob Herring
2021-04-20  0:35       ` Leonardo Bras
2021-04-20  1:39         ` Rob Herring
2021-04-20  2:02           ` Leonardo Bras
2021-04-20 22:34             ` Rob Herring
2021-04-21 14:14               ` Leonardo Bras
2021-04-16 21:27   ` Leonardo Bras
2021-06-09 18:50   ` Bjorn Helgaas
2021-04-21 12:51 ` Rob Herring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210421125157.GA967343@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=aik@ozlabs.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=leobras.c@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).