mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
	conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	linux@roeck-us.net, lkft-triage@lists.linaro.org,
	patches@kernelci.org, patches@lists.linux.dev,
	pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
	sr@sladewatkins.com, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
	"Arve Hjønnevåg" <arve@android.com>,
	"Todd Kjos" <tkjos@android.com>,
	"Christian Brauner" <christian@brauner.io>,
	"Carlos Llamas" <cmllamas@google.com>,
	"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH 7.2 000/428] 7.2.10-rc1 review
Date: Sun, 11 Oct 2026 16:17:30 +0200	[thread overview]
Message-ID: <2026101103-fling-stipulate-084f@gregkh> (raw)
In-Reply-To: <CANiq72ndhLush3bugar1YGPnsein8min1k3_NucBxzFwCWe9Ug@mail.gmail.com>

On Sun, Oct 11, 2026 at 04:11:48PM +0200, Miguel Ojeda wrote:
> On Sun, Oct 11, 2026 at 3:10 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Seems to be broken by "rust_binder: reschedule node refcount update on
> > thread exit" as removing that fixes the builds which I did.  Any
> > objection to that?
> 
> Yeah, it is that one.
> 
> In case it helps, I am re-running my CI with the extra parameter
> manually removed in those two calls (instead of dropping that commit),
> to see if the rest builds and runs fine after that issue, and it looks
> OK in all the builds that completed so far.

If that works, can you, or someone else, send an updated version of that
commit for the next round of stable releases as I dropped it for this
one.

thanks,

greg k-h

  reply	other threads:[~2026-10-11 14:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 14:05 Greg Kroah-Hartman
2026-10-09 14:53 ` Brett A C Sheffield
2026-10-09 15:14 ` Ronald Warsow
2026-10-09 22:22 ` Peter Schneider
2026-10-10  7:19 ` Ron Economos
2026-10-10 13:29 ` Takeshi Ogasawara
2026-10-11  1:25 ` Slade Watkins
2026-10-11  8:25 ` Barry K. Nathan
2026-10-11 11:13 ` Miguel Ojeda
2026-10-11 13:10   ` Greg KH
2026-10-11 14:11     ` Miguel Ojeda
2026-10-11 14:17       ` Greg KH [this message]
2026-10-11 16:39         ` Miguel Ojeda
2026-10-11 21:07 ` Pavel Machek

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=2026101103-fling-stipulate-084f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=broonie@kernel.org \
    --cc=christian@brauner.io \
    --cc=cmllamas@google.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tkjos@android.com \
    --cc=torvalds@linux-foundation.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®