[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240913171729.6bf3de40@kernel.org>
Date: Fri, 13 Sep 2024 17:17:29 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mina Almasry <almasrymina@...gle.com>
Cc: Matthew Wilcox <willy@...radead.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Jesper Dangaard Brouer <hawk@...nel.org>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Stephen Rothwell
<sfr@...b.auug.org.au>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH net-next v2] page_pool: fix build on powerpc with GCC 14
On Fri, 13 Sep 2024 15:20:13 -0700 Mina Almasry wrote:
> I have not reported the issue to GCC yet. From the build break thread
> it seemed a fix was urgent, so I posted the fix and was planning to
> report the issue after. If not, no problem, I'll report the issue and
> repost the fix with a GCC bugzilla link, waiting 24hr before reposts
> this time.
I should have clarified, the "please post ASAP" applies
to all devmem build fixes, ignore the cool down period :)
> I just need to go through the steps in https://gcc.gnu.org/bugs/,
> shouldn't be an issue.
Just post the link here, I'll add it to the commit msg when applying.
Powered by blists - more mailing lists