From: Christian Brauner <brauner@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Askar Safin <safinaskar@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] init/initramfs.c: trivial fix: FSM -> Finite-state machine
Date: Mon, 23 Mar 2026 13:09:23 +0100 [thread overview]
Message-ID: <20260323-tierisch-schnupfen-5ff1d33507fc@brauner> (raw)
In-Reply-To: <20260320144635.GA6202@frogsfrogsfrogs>
On Fri, Mar 20, 2026 at 07:46:35AM -0700, Darrick J. Wong wrote:
> On Thu, Mar 19, 2026 at 11:27:21PM +0000, Askar Safin wrote:
> > FSM means "finite-state machine", but I think this is not obvious to
> > everyone.
> >
> > Signed-off-by: Askar Safin <safinaskar@gmail.com>
> > ---
> > init/initramfs.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/init/initramfs.c b/init/initramfs.c
> > index 139baed06..d29fe0a5c 100644
> > --- a/init/initramfs.c
> > +++ b/init/initramfs.c
> > @@ -212,7 +212,7 @@ static void __init parse_header(char *s)
> > hdr_csum = parsed[12];
> > }
> >
> > -/* FSM */
>
> ...and here I thought all along that the initramfs code had been blessed
> by the flying spaghetti monster! ;)
I've touched it a lot recently and the urge to massage it is getting
stronger but I have too much other stuff to do...
prev parent reply other threads:[~2026-03-23 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 23:27 [PATCH] init/initramfs.c: trivial fix: FSM -> Finite-state machine Askar Safin
2026-03-20 13:16 ` Christian Brauner
2026-03-20 14:46 ` Darrick J. Wong
2026-03-23 12:09 ` Christian Brauner [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=20260323-tierisch-schnupfen-5ff1d33507fc@brauner \
--to=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=safinaskar@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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