From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: Aldo Ariel Panzardo <qwe.aldo@gmail.com>,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] nilfs2: validate file block counts during recovery
Date: Fri, 18 Sep 2026 20:01:26 -0700 [thread overview]
Message-ID: <2f638ff0568a55233899b2a7ef4dba3ed945bc51.camel@dubeyko.com> (raw)
In-Reply-To: <CAKFNMo=0-rxN0BKG1v+KhrGwnh2ZL_Hn2Jbcqc9sWRV8cwxPrQ@mail.gmail.com>
On Sat, 2026-09-19 at 09:46 +0900, Ryusuke Konishi wrote:
> On Sat, Sep 19, 2026 at 4:33 AM Viacheslav Dubeyko wrote:
> >
> > On Sat, 2026-09-19 at 00:44 +0900, Ryusuke Konishi wrote:
> > > Also, please replace the 'Cc: stable' tag with the following tag,
> > > as
> > > with the previous patch:
> > >
> > > Cc: stable+noautosel@kernel.org # Non-fatal bug fix; defer
> > > backport
> > > until a real issue is reported
> >
> > Damn! I missed this request. I already pushed the commit. Are you
> > OK
> > with that? :)
>
> Viacheslav,
>
> Since we haven't hit the merge window yet, and linux-next (the
> destination where your for-next branch is integrated) is a daily
> integration tree intended to be rebased before being pulled into
> Linus's tree, updating the commit message on your branch now should
> be
> completely fine.
>
> As documented in Documentation/maintainer/rebasing-and-merging.rst:
> "Some trees (linux-next being a significant example) are frequently
> rebased by their nature..."
>
> I think it would be better to fix the tag and overwrite-push it now
> rather than leaving it as is, though of course it will need to be
> frozen once we hit the merge window (or after the official release).
>
Sorry, I have too busy day.
The commit message has been updated and pushed.
Thanks,
Slava.
next prev parent reply other threads:[~2026-09-19 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 11:13 Aldo Ariel Panzardo
2026-09-15 19:46 ` Viacheslav Dubeyko
2026-09-15 19:56 ` Aldo Ariel Panzardo
2026-09-15 19:57 ` [PATCH v2] " Aldo Ariel Panzardo
2026-09-16 19:10 ` Viacheslav Dubeyko
2026-09-18 15:44 ` [PATCH] " Ryusuke Konishi
2026-09-18 19:33 ` Viacheslav Dubeyko
2026-09-19 0:46 ` Ryusuke Konishi
2026-09-19 3:01 ` Viacheslav Dubeyko [this message]
2026-09-19 3:07 ` Ryusuke Konishi
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=2f638ff0568a55233899b2a7ef4dba3ed945bc51.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=qwe.aldo@gmail.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®