From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B2103C19F28 for ; Wed, 3 Aug 2022 17:50:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238612AbiHCRuW (ORCPT ); Wed, 3 Aug 2022 13:50:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238413AbiHCRuV (ORCPT ); Wed, 3 Aug 2022 13:50:21 -0400 Received: from mx.cjr.nz (mx.cjr.nz [51.158.111.142]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9FD5E38B0 for ; Wed, 3 Aug 2022 10:50:15 -0700 (PDT) Received: from authenticated-user (mx.cjr.nz [51.158.111.142]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pc) by mx.cjr.nz (Postfix) with ESMTPSA id D4A4B7FD17; Wed, 3 Aug 2022 17:50:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cjr.nz; s=dkim; t=1659549012; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MA+gnPofh7m0h90TueToyzo3t+yzml63JRNV5q5y+mM=; b=H8pbMXoR4BHlmgxonNr793NznJqZ9uF2fbyp4ntsh0kwo/o82AcslpT6B9H2AbXRXmPs5P TG+PG3ohHvY+M1ZIWTOTJ4yFSDVgfiQLJ4M3iDmlOIPxjJrxkxFP1uR4/qPb5vbYOOdFG2 IMba8Ecuw1yIW4+GtisxxRPoTxdqgZvLqNlkl6K48rNPkPrF4MuC2T+kS2WILNKkPW0IfJ Lv7xgBOUBm3DRAsMeDs2PvCDCWfhyxxdjLdIxPFYeuEDGAnsPN4qVsmgm/kOyodA9DQiZW fkznHdHsqsrAbxXVOoYvgkyY/aAxhLOItY6Nyhde6silCD1nzBTlotJZv/fhSQ== From: Paulo Alcantara To: Enzo Matsumiya , Jeff Layton 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" In-Reply-To: <20220803144519.rn6ybbroedgmuaie@cyberdelia> References: <20220801190933.27197-1-ematsumiya@suse.de> <20220802193620.dyvt5qiszm2pobsr@cyberdelia> <6f3479265b446d180d71832fd0c12650b908ebe2.camel@kernel.org> <20220803144519.rn6ybbroedgmuaie@cyberdelia> Date: Wed, 03 Aug 2022 14:50:17 -0300 Message-ID: <87fsidnrmu.fsf@cjr.nz> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-cifs@vger.kernel.org Enzo Matsumiya 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.