From: Jan Kara <jack@suse.cz>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Piotr Siminski <piotr.siminski@globallogic.com>,
Jan Kara <jack@suse.cz>,
reiserfs-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: change reiserfs status to obsolete
Date: Mon, 31 Jul 2023 19:11:31 +0200 [thread overview]
Message-ID: <20230731171131.qpaoz7i3cto5wxyv@quack3> (raw)
In-Reply-To: <CAKXUXMzL4i0jT0xPFsV4ZG6L82yDCYLtKoUL7t=21ZDZ4OMY7w@mail.gmail.com>
On Thu 20-07-23 13:57:18, Lukas Bulwahn wrote:
> Piotr, thanks for the clean up in the MAINTAINERS file.
>
> Reviewed-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
>
> Jan, could you pick this patch?
Yes, picked up now. Thanks!
Honza
>
> Lukas
>
>
> On Thu, Jul 20, 2023 at 1:54 PM Piotr Siminski
> <piotr.siminski@globallogic.com> wrote:
> >
> > Reiserfs file system is no longer supported and is going to be removed
> > in 2025 as stated in commit eb103a51640e ("reiserfs: Deprecate reiserfs").
> >
> > Signed-off-by: Piotr Siminski <piotr.siminski@globallogic.com>
> > ---
> > MAINTAINERS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index a5c16bb92fe2..c340c6fc7923 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -18064,7 +18064,7 @@ F: include/linux/regmap.h
> >
> > REISERFS FILE SYSTEM
> > L: reiserfs-devel@vger.kernel.org
> > -S: Supported
> > +S: Obsolete
> > F: fs/reiserfs/
> >
> > REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM
> > --
> > 2.34.1
> >
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2023-07-31 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:54 [PATCH] MAINTAINERS: change reiserfs status to obsolete Piotr Siminski
2023-07-20 11:57 ` Lukas Bulwahn
2023-07-31 17:11 ` Jan Kara [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=20230731171131.qpaoz7i3cto5wxyv@quack3 \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=piotr.siminski@globallogic.com \
--cc=reiserfs-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).