From: Florian Fainelli <f.fainelli@gmail.com>
To: Alex Elder <elder@ieee.org>, Alex Elder <elder@linaro.org>,
davem@davemloft.net, kuba@kernel.org
Cc: bjorn.andersson@linaro.org, evgreen@chromium.org,
cpratapa@codeaurora.org, subashab@codeaurora.org,
elder@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/4] net: ipa: introduce dma_addr_high32()
Date: Wed, 17 Mar 2021 16:00:33 -0700 [thread overview]
Message-ID: <f0215cf7-3a62-421c-28bf-17aa4e197b9b@gmail.com> (raw)
In-Reply-To: <60106d7b-ad70-01fa-9f90-fe384cc428f8@ieee.org>
On 3/17/2021 3:49 PM, Alex Elder wrote:
> On 3/17/21 5:47 PM, Florian Fainelli wrote:
>>> +/* Encapsulate extracting high-order 32 bits of DMA address */
>>> +static u32 dma_addr_high32(dma_addr_t addr)
>>> +{
>>> +#ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT
>>> + return (u32)(addr >> 32);
>> You can probably use upper_32bits() here...
>
> Where is that defined? I'd be glad to use it. -Alex
include/linux/kernel.h, and it is upper_32_bits() and lower_32_bits()
sorry about the missing space.
--
Florian
next prev parent reply other threads:[~2021-03-17 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 22:29 [PATCH net-next 0/4] net: ipa: support 32-bit targets Alex Elder
2021-03-17 22:29 ` [PATCH net-next 1/4] net: ipa: fix assumptions about DMA address size Alex Elder
2021-03-17 22:29 ` [PATCH net-next 2/4] net: ipa: introduce dma_addr_high32() Alex Elder
2021-03-17 22:47 ` Florian Fainelli
2021-03-17 22:49 ` Alex Elder
2021-03-17 23:00 ` Florian Fainelli [this message]
2021-03-18 13:33 ` Alex Elder
2021-03-17 22:29 ` [PATCH net-next 3/4] net: ipa: fix table alignment requirement Alex Elder
2021-03-17 22:29 ` [PATCH net-next 4/4] net: ipa: relax 64-bit build requirement Alex Elder
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=f0215cf7-3a62-421c-28bf-17aa4e197b9b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@ieee.org \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.