From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Andy Shevchenko <andriy.shevchenko@linux•intel.com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
George Abraham P <george.abraham.p@intel•com>,
Herbert Xu <herbert@gondor•apana.org.au>
Subject: Re: linux-next: build failure after merge of all the trees
Date: Tue, 22 Jul 2025 08:24:11 +1000 [thread overview]
Message-ID: <20250722082411.130825e0@canb.auug.org.au> (raw)
In-Reply-To: <20250721141336.1491a3b5b09529171d65db6f@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hi Andrew,
On Mon, 21 Jul 2025 14:13:36 -0700 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> On Mon, 21 Jul 2025 14:42:22 +0300 Andy Shevchenko <andriy.shevchenko@linux•intel.com> wrote:
>
> > > Is there any good reason not to do this?
> > >
> > > I guess this patch should have
> > >
> > > Fixes: 39ced19b9e60 ("lib/vsprintf: split out sprintf() and friends")
> >
> > This sounds correct to me and your patch should be sent as a fix to the stable
> > kernels as well.
>
> Yep, thanks, I added the cc:stable, queued it up and shall send to
> Linus this week.
Thanks, I was going to get around to that this morning. One less thing
to do :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-07-21 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 7:37 linux-next: build failure after merge of all the trees Stephen Rothwell
2025-07-21 11:42 ` Andy Shevchenko
2025-07-21 21:13 ` Andrew Morton
2025-07-21 22:24 ` Stephen Rothwell [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=20250722082411.130825e0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=george.abraham.p@intel$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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