From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Fri, 23 Feb 2018 08:19:28 +0000 Subject: Re: [0/8] target-iSCSI: Adjustments for several function implementations Message-Id: List-Id: References: <6163538d-a406-2f60-11a2-88b4694e9975@users.sourceforge.net> <20180222143624.7c7241a1@suse.de> In-Reply-To: <20180222143624.7c7241a1@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: David Disseldorp , target-devel@vger.kernel.org, linux-scsi@vger.kernel.org Cc: kernel-janitors@vger.kernel.org, LKML , Al Viro , Arun Easi , Bart Van Assche , Dan Carpenter , Hannes Reinecke , Ingo Molnar , "Jason A. Donenfeld" , Jiang Yi , Kees Cook , "Nicholas A. Bellinger" , Russell King , Tang Wenji , Theodore Ts'o , Varun Prakash > You're 1/8 patch had an actual bug fix hidden amongst the style churn. It showed the general possibility to adjust the source code structure for the function “chap_server_compute_md5” also because of the usage of the single jump label “out” before. > I don't see any such fixes in the other patches. This view is appropriate. Further update steps show different transformation possibilities. > My opinion from https://www.spinics.net/lists/target-devel/msg16342.html > hasn't changed. FWIW, I'd prefer to see LIO adopt a policy similar to: > https://btrfs.wiki.kernel.org/index.php/Developer%27s_FAQ#How_not_to_start It seems that you express a few aspects for general change resistance. Will the circumstances evolve for similar software improvements? Regards, Markus