From: Matthew Brost <matthew.brost@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Usama Arif <usama.arif@linux.dev>, <linux-mm@kvack.org>,
<dri-devel@lists.freedesktop.org>, <linux-next@vger.kernel.org>
Subject: Re: Semantic conflict between 04b177544a04 in drm-misc-fixes and 0b6b1bb28482 in -mm
Date: Fri, 24 Jul 2026 12:50:46 -0700 [thread overview]
Message-ID: <amPCFgiNkCIRuGk9@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260724194808.GA1461047@ax162>
On Fri, Jul 24, 2026 at 12:48:08PM -0700, Nathan Chancellor wrote:
> On Fri, Jul 24, 2026 at 01:13:42AM +0100, Mark Brown wrote:
> > On Thu, Jul 23, 2026 at 04:11:48PM -0700, Matthew Brost wrote:
> > > On Thu, Jul 23, 2026 at 04:09:42PM -0700, Andrew Morton wrote:
> >
> > > > I'm fine the drm people changing things ;)
> >
> > > I'll jump make a DRM change so this is all worked out when it gets to
> > > Linus.
> >
> > So should I drop Nathan's fixup then?
>
> As you may or may not have seen yet, the drm commit has been reverted in
> the drm-misc-fixes branch, so my change should no longer apply.
Yes, I asked to drm-misc-fixes maintainer to revert the change to avoid
sending to Linus and will post a non-conflicting follow up drm shortly.
Matt
>
> --
> Cheers,
> Nathan
prev parent reply other threads:[~2026-07-24 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 22:56 Semantic conflict between 04b177544a04 in drm-misc-fixes and 0b6b1bb28482 in -mm Nathan Chancellor
2026-07-22 23:15 ` Matthew Brost
2026-07-23 21:27 ` Nathan Chancellor
2026-07-23 23:09 ` Andrew Morton
2026-07-23 23:11 ` Matthew Brost
2026-07-24 0:13 ` Mark Brown
2026-07-24 19:48 ` Nathan Chancellor
2026-07-24 19:50 ` Matthew Brost [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=amPCFgiNkCIRuGk9@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=tzimmermann@suse.de \
--cc=usama.arif@linux.dev \
/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