From: patchwork-bot+netdevbpf@kernel.org
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@openeuler.org,
hawk@kernel.org, ilias.apalodimas@linaro.org,
akpm@linux-foundation.org, peterz@infradead.org, vbabka@suse.cz,
willy@infradead.org, will@kernel.org, feng.tang@intel.com,
jgg@ziepe.ca, ebiederm@xmission.com, aarcange@redhat.com,
guillaume.tucker@collabora.com
Subject: Re: [PATCH net] page_pool: Revert "page_pool: disable dma mapping support..."
Date: Thu, 18 Nov 2021 11:40:09 +0000 [thread overview]
Message-ID: <163723560952.11739.1415863024804247853.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211117075652.58299-1-linyunsheng@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 17 Nov 2021 15:56:52 +0800 you wrote:
> This reverts commit d00e60ee54b12de945b8493cf18c1ada9e422514.
>
> As reported by Guillaume in [1]:
> Enabling LPAE always enables CONFIG_ARCH_DMA_ADDR_T_64BIT
> in 32-bit systems, which breaks the bootup proceess when a
> ethernet driver is using page pool with PP_FLAG_DMA_MAP flag.
> As we were hoping we had no active consumers for such system
> when we removed the dma mapping support, and LPAE seems like
> a common feature for 32 bits system, so revert it.
>
> [...]
Here is the summary with links:
- [net] page_pool: Revert "page_pool: disable dma mapping support..."
https://git.kernel.org/netdev/net/c/f915b75bffb7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-18 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 7:56 Yunsheng Lin
2021-11-17 10:28 ` Guillaume Tucker
2021-11-17 11:48 ` Jesper Dangaard Brouer
2021-11-17 11:51 ` Ilias Apalodimas
2021-11-18 11:40 ` patchwork-bot+netdevbpf [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=163723560952.11739.1415863024804247853.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=feng.tang@intel.com \
--cc=guillaume.tucker@collabora.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®