public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Peter Lafreniere <peter@n8pjl.ca>, linux-sh@vger.kernel.org
Cc: jack@suse.cz, reiserfs-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] arch: sh: remove ReiserFS from defconfig
Date: Tue, 24 Oct 2023 18:46:11 +0200	[thread overview]
Message-ID: <ee30c656c3e3b027edcfa4bc2947cea192f5cd2d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20230918175529.19011-4-peter@n8pjl.ca>

Hi Peter!

On Mon, 2023-09-18 at 17:56 +0000, Peter Lafreniere wrote:
> ReiserFS has been deprecated for a year and a half, yet is still built
> as part of a defconfig kernel.
> 
> According to commit eb103a51640e ("reiserfs: Deprecate reiserfs"), the
> filesystem is slated to be removed in 2025. Remove it from the defconfig
> profiles now, as part of its deprecation process.
> 
> Signed-off-by: Peter Lafreniere <peter@n8pjl.ca>
> ---
>  arch/sh/configs/landisk_defconfig | 1 -
>  arch/sh/configs/titan_defconfig   | 1 -
>  2 files changed, 2 deletions(-)
> 
> diff --git a/arch/sh/configs/landisk_defconfig b/arch/sh/configs/landisk_defconfig
> index 541082090918..af1ab25227e3 100644
> --- a/arch/sh/configs/landisk_defconfig
> +++ b/arch/sh/configs/landisk_defconfig
> @@ -94,7 +94,6 @@ CONFIG_USB_SISUSBVGA=m
>  CONFIG_EXT2_FS=y
>  CONFIG_EXT3_FS=y
>  # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
> -CONFIG_REISERFS_FS=y
>  CONFIG_ISO9660_FS=m
>  CONFIG_MSDOS_FS=y
>  CONFIG_VFAT_FS=y
> diff --git a/arch/sh/configs/titan_defconfig b/arch/sh/configs/titan_defconfig
> index 871092753591..50e378adc4c5 100644
> --- a/arch/sh/configs/titan_defconfig
> +++ b/arch/sh/configs/titan_defconfig
> @@ -221,7 +221,6 @@ CONFIG_EXT2_FS=y
>  CONFIG_EXT3_FS=y
>  # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
>  # CONFIG_EXT3_FS_XATTR is not set
> -CONFIG_REISERFS_FS=m
>  CONFIG_XFS_FS=m
>  CONFIG_FUSE_FS=m
>  CONFIG_ISO9660_FS=m

What has been the feedback so far on this? Do most maintainer remove it or not?

I don't have a strong opinion on this, but I tend to keep it in defconfig until
ReiserFS has been completely removed from the kernel.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-10-24 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 17:56 [PATCH 0/7] arch/*: config: Remove ReiserFS from defconfig Peter Lafreniere
2023-09-18 17:56 ` [PATCH 3/7] arch: sh: remove " Peter Lafreniere
2023-10-24 16:46   ` John Paul Adrian Glaubitz [this message]
2023-10-24 17:45     ` Peter Lafreniere
2023-09-18 23:41 ` [PATCH 0/7] arch/*: config: Remove " Segher Boessenkool
2023-09-19  0:00   ` Peter Lafreniere
2023-09-19 15:16     ` Segher Boessenkool
2023-09-19 15:58       ` Peter Lafreniere
2023-09-19 16:02         ` Geert Uytterhoeven
2023-09-19 16:15           ` Peter Lafreniere
2023-09-20  9:30             ` Geert Uytterhoeven
2023-09-20 16:56           ` Jan Kara
2023-10-15 10:04 ` (subset) " Michael Ellerman

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=ee30c656c3e3b027edcfa4bc2947cea192f5cd2d.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=peter@n8pjl.ca \
    --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