From: Daniel Vetter <daniel@ffwll.ch>
To: Mark Brown <broonie@kernel.org>, Dave Airlie <airlied@gmail.com>
Cc: "Intel Graphics" <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christian König" <christian.koenig@amd.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: linux-next: manual merge of the drm-misc tree with the mm-stable tree
Date: Wed, 19 Apr 2023 18:24:37 +0200 [thread overview]
Message-ID: <ZEAVxeIEOny81EGY@phenom.ffwll.local> (raw)
In-Reply-To: <8c90b4db-3075-4275-bea8-01f501b00885@sirena.org.uk>
On Tue, Apr 18, 2023 at 07:34:44PM +0100, Mark Brown wrote:
> On Sun, Apr 16, 2023 at 09:58:50AM +0200, Daniel Vetter wrote:
>
> > Note there was a ppc compile fail, which is why we pushed the ttm revert.
> > That /should/ be fixed now, but would be good if you can confirm?
>
> According to Nathan (CCed) there's still issues with the interaction
> with the PowerPC tree.
So this revert was supposed to fix this: 56e51681246e ("drm/ttm: revert
"Reduce the number of used allocation orders for TTM pages"")
If there's anything left then I need to chase that asap since the merge
window will open soon.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-04-19 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 12:59 linux-next: manual merge of the drm-misc tree with the mm-stable tree broonie
2023-04-16 7:58 ` Daniel Vetter
2023-04-17 11:34 ` Mark Brown
2023-04-18 18:34 ` Mark Brown
2023-04-19 16:24 ` Daniel Vetter [this message]
2023-04-19 16:30 ` Nathan Chancellor
2023-04-19 16:32 ` Daniel Vetter
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=ZEAVxeIEOny81EGY@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nathan@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