public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead•org>
To: Mark Brown <broonie@kernel•org>
Cc: Thomas Gleixner <tglx@kernel•org>, Ingo Molnar <mingo@kernel•org>,
	"H. Peter Anvin" <hpa@zytor•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: Fixes tag needs work in the tip tree
Date: Fri, 16 Jan 2026 13:40:33 +0100	[thread overview]
Message-ID: <20260116124033.GB1890602@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <0fe6b4c2-373f-4b26-a878-6bd686c55d67@sirena.org.uk>

On Fri, Jan 16, 2026 at 12:28:34PM +0000, Mark Brown wrote:
> Hi,
> 
> In commit
> 
>   69044a0cbfdcc ("x86/uprobes: Fix XOL allocation failure for 32-bit tasks")
> 
> Fixes tag
> 
>   Fixes: 1b028f784e8c ("86/mm: Introduce mmap_compat_base() for 32-bit mmap()")
> 

Moo.. let me force push that commit again. That's a single character
gone walk-about.

      reply	other threads:[~2026-01-16 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 12:28 Fixes tag needs work in the tip tree Mark Brown
2026-01-16 12:40 ` Peter Zijlstra [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=20260116124033.GB1890602@noisy.programming.kicks-ass.net \
    --to=peterz@infradead$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@kernel$(echo .)org \
    --cc=tglx@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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