All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@cjr.nz>
To: Enzo Matsumiya <ematsumiya@suse.de>, Jeff Layton <jlayton@kernel.org>
Cc: linux-cifs@vger.kernel.org, smfrench@gmail.com,
	ronniesahlberg@gmail.com, nspmangalore@gmail.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	tom@talpey.com, samba-technical@lists.samba.org,
	pshilovsky@samba.org
Subject: Re: [RFC PATCH 0/3] Rename "cifs" module to "smbfs"
Date: Wed, 03 Aug 2022 14:50:17 -0300	[thread overview]
Message-ID: <87fsidnrmu.fsf@cjr.nz> (raw)
In-Reply-To: <20220803144519.rn6ybbroedgmuaie@cyberdelia>

Enzo Matsumiya <ematsumiya@suse.de> writes:

> A note on backports: I myself (and Paulo) do the backports for our SLE
> products, sometimes down to SLE11-SP4 (based on kernel 3.0) and I
> could not see what other issues could appear given if we backport this
> rename to released products.
>
> Of course, I don't know every process for every distro vendors, so if
> someone could provide feedback on this, I'd appreciate.
>
> @Paulo I'd like to hear your opinion on possible issues of future backports,
> if we backported this rename patch to SLES.

We all know that backports aren't usually easy to deal with --
especially when doing them on very old kernels.  So, if we're gonna make
them even more difficult, there must be a good reason like a new feature
or bugfix.  This rename simply doesn't justify all the trouble, IMO.

Besides, for any future fixes marked for stable after this rename, it's
gonna be tricky as well.  Of course, we can definitely handle them but
not worth the trouble, too.

Just to be clear, this is a NAK from me.

      reply	other threads:[~2022-08-03 17:50 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 19:09 [RFC PATCH 0/3] Rename "cifs" module to "smbfs" Enzo Matsumiya
2022-08-01 19:09 ` [RFC PATCH 1/3] cifs: change module name to "smbfs.ko" Enzo Matsumiya
2023-07-26 20:28   ` Steve French
2023-07-26 20:29     ` Steve French
2023-07-26 20:31       ` Steve French
2023-07-27  0:24         ` Enzo Matsumiya
2022-08-01 19:09 ` [RFC PATCH 2/3] smbfs: rename directory "fs/cifs" -> "fs/smbfs" Enzo Matsumiya
2022-08-01 19:09 ` [RFC PATCH 3/3] smbfs: update doc references Enzo Matsumiya
2022-08-01 19:58 ` [RFC PATCH 0/3] Rename "cifs" module to "smbfs" Rowland Penny
2022-08-01 20:14   ` Enzo Matsumiya
2022-08-01 20:27     ` Steve French
2022-08-01 20:41       ` Enzo Matsumiya
2022-08-02  0:38     ` Tom Talpey
2022-08-02  0:42       ` Steve French
2022-08-02 13:52       ` Enzo Matsumiya
2022-08-02 15:35         ` Steve French
2022-08-02 15:58           ` Enzo Matsumiya
2022-08-02 16:20             ` Steve French
2022-08-02 17:43             ` Tom Talpey
2022-08-02 14:42 ` Jeff Layton
2022-08-02 19:36   ` Enzo Matsumiya
2022-08-02 20:07     ` Jeff Layton
2022-08-03  1:32       ` Tom Talpey
2022-08-03  1:56         ` Enzo Matsumiya
2022-08-04 19:03           ` Jeff Layton
2022-08-04 20:23             ` Matthew Wilcox
2022-08-04 20:48               ` Jeff Layton
2022-08-03  5:38         ` Steve French
2022-08-03 14:45       ` Enzo Matsumiya
2022-08-03 17:50         ` Paulo Alcantara [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=87fsidnrmu.fsf@cjr.nz \
    --to=pc@cjr.nz \
    --cc=ematsumiya@suse.de \
    --cc=jlayton@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=pshilovsky@samba.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=samba-technical@lists.samba.org \
    --cc=smfrench@gmail.com \
    --cc=tom@talpey.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.