From: Carlos Maiolino <cem@kernel.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "djwong@kernel.org" <djwong@kernel.org>,
"dchinner@redhat.com" <dchinner@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: Fix duplicate assignment in xfs_alloc_read_agf.
Date: Wed, 21 Oct 2026 14:11:15 +0200 [thread overview]
Message-ID: <atirYb9qxRsaRYhs@cronus.toxiclabs.cc> (raw)
In-Reply-To: <e7feec9bf096ed64f581536aa314a21723cccc63.camel@oracle.com>
On Thu, Oct 15, 2026 at 12:56:43PM +0000, Siddh Raman Pant wrote:
> On Tue, Oct 13 2026 at 20:01:04 +0530, Carlos Maiolino wrote:
> > On Thu, Oct 01, 2026 at 08:21:53PM +0530, Siddh Raman Pant wrote:
> > > Probably an (harmless) error in copy-paste.
> > >
> > > Fixes: db6a2274162d ("xfs: catch stale AGF/AGF metadata")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Siddh Raman Pant <siddh.raman.pant@oracle.com>
> > > ---
> > > Put in stables <= 6.12 after the backport series lands.
> >
> > Fix the tags accordingly to Darrick's review and re-send please.
> >
>
> I have sent some backports for remaining kernels and I would like this
> to go into them too once they land. Should I still do it?
Probably. You've gotta tell stable this patch should land there in some
way. I think they are looking into those tags to guide them what
versions this should be backported to.
>
> Thanks,
> Siddh
next prev parent reply other threads:[~2026-10-21 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 14:51 Siddh Raman Pant
2026-10-01 14:58 ` Darrick J. Wong
2026-10-13 14:31 ` Carlos Maiolino
2026-10-13 14:33 ` Darrick J. Wong
2026-10-15 12:56 ` Siddh Raman Pant
2026-10-21 12:11 ` Carlos Maiolino [this message]
2026-10-21 12:16 ` [PATCH v2] " Siddh Raman Pant
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=atirYb9qxRsaRYhs@cronus.toxiclabs.cc \
--to=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=siddh.raman.pant@oracle.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®