public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: David Disseldorp <ddiss@suse.de>,
	target-devel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Arun Easi <arun.easi@cavium.com>,
	Bart Van Assche <bart.vanassche@sandisk.com>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Hannes Reinecke <hare@suse.com>, Ingo Molnar <mingo@kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Jiang Yi <jiangyilism@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Tang Wenji <tang.wenji@zte.com.cn>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Varun Prakash <varun@chelsio.com>
Subject: Re: [0/8] target-iSCSI: Adjustments for several function implementations
Date: Fri, 23 Feb 2018 09:19:28 +0100	[thread overview]
Message-ID: <da62858f-37f5-1396-c561-ab68ba20c811@users.sourceforge.net> (raw)
In-Reply-To: <20180222143624.7c7241a1@suse.de>

> 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

  parent reply	other threads:[~2018-02-23  8:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 21:40 [PATCH 0/8] target-iSCSI: Adjustments for several function implementations SF Markus Elfring
2017-12-12 21:42 ` [PATCH 1/8] target/iscsi: Less function calls in chap_server_compute_md5() after error detection SF Markus Elfring
2017-12-12 21:43 ` [PATCH 2/8] target/iscsi: Move resetting of seven variables in chap_server_compute_md5() SF Markus Elfring
2017-12-12 21:45 ` [PATCH 3/8] target/iscsi: Delete 36 error messages for a failed memory allocation SF Markus Elfring
2017-12-12 21:46 ` [PATCH 4/8] target/iscsi: Delete an unnecessary variable initialisation in iscsit_allocate_ooo_cmdsn() SF Markus Elfring
2017-12-12 21:47 ` [PATCH 5/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_copy_param_list() SF Markus Elfring
2017-12-12 21:49 ` [PATCH 6/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_create_default_params() SF Markus Elfring
2017-12-12 21:50 ` [PATCH 7/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_set_default_param() SF Markus Elfring
2017-12-12 21:52 ` [PATCH 8/8] target/iscsi: Improve 16 size determinations SF Markus Elfring
2018-02-21 16:45 ` [PATCH 0/8] target-iSCSI: Adjustments for several function implementations SF Markus Elfring
     [not found]   ` <20180222143624.7c7241a1@suse.de>
2018-02-23  8:19     ` SF Markus Elfring [this message]
     [not found]     ` <20180222135600.5vv7vzw7sa5metcb@mwanda>
2018-02-23  9:06       ` [0/8] " SF Markus Elfring
2018-02-23 10:17         ` Dan Carpenter
2018-02-23 11:50           ` SF Markus Elfring

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=da62858f-37f5-1396-c561-ab68ba20c811@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=Jason@zx2c4.com \
    --cc=arun.easi@cavium.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=dan.carpenter@oracle.com \
    --cc=ddiss@suse.de \
    --cc=hare@suse.com \
    --cc=jiangyilism@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=tang.wenji@zte.com.cn \
    --cc=target-devel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=varun@chelsio.com \
    --cc=viro@zeniv.linux.org.uk \
    /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