[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd69629f-abf4-cc03-dddb-b2f3e7cb92fd@users.sourceforge.net>
Date: Fri, 7 Oct 2016 18:38:52 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Jiri Kosina <jikos@...nel.org>
Cc: "Austin S. Hemmelgarn" <ahferroin7@...il.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
Richard Weinberger <richard@....at>,
linux-raid@...r.kernel.org, Christoph Hellwig <hch@....de>,
Guoqing Jiang <gqjiang@...e.com>, Jens Axboe <axboe@...com>,
Mike Christie <mchristi@...hat.com>,
Neil Brown <neilb@...e.com>, Shaohua Li <shli@...nel.org>,
Tomasz Majchrzak <tomasz.majchrzak@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: md/raid1: Improve another size determination in setup_conf()
>>> but patches that just fix coding style are a bad thing
>>
>> When you find such a change opportunity so "bad", are there any
>> circumstances left over where you would dare to touch the corresponding
>> source code line.
>
> If you actually rewrite the code or fix some real bug there.
Do the proposed update steps 12 - 16 for the function "setup_conf"
(in this software module) fit to your condition?
Do you reject this update step?
Regards,
Markus
Powered by blists - more mailing lists