From: Markus Elfring <Markus.Elfring@web.de>
To: Enrico Weigelt <lkml@metux.net>, kernel-janitors@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Lee Jones <lee.jones@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mfd: asic3: One function call less in asic3_irq_probe()
Date: Mon, 8 Jul 2019 13:50:49 +0200 [thread overview]
Message-ID: <b116fc90-9558-8609-d803-7d8da2b66e0a@web.de> (raw)
In-Reply-To: <6e8eab5f-1f5c-b3dc-6b65-96a874ec2789@metux.net>
>> I suggest to reduce a bit of duplicate source code also at this place.
>
> Duplicate code (logic) or just characters ?
Both.
> IMHO, readability is an important aspect, so we could be careful about that.
This is usual.
The code text size can influence this aspect in considerable ways.
>> We can have different opinions about the criteria which are relevant here.
>
> Which criterias are you operating on ?
I suggest occasionally again to reconsider consequences around a principle
like “Don't repeat yourself”.
> I think it's good that you're using tools like cocci for pointing out
> *possible* points of useful refactoring.
Thanks for your general understanding.
> But that doesn't mean that a particular patch can be accepted
> or not in the greater context.
Would you like to find the corresponding change acceptance out at all?
> Note that such issues are pretty subjective
The situation depends on some factors.
> - it's not a technical
I got an other impression.
> but an asthetic matter,
This matters also.
> so such issues can't be resolved by logic.
I guess that it can help.
Regards,
Markus
next prev parent reply other threads:[~2019-07-08 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 18:30 [PATCH] " Markus Elfring
2019-07-07 0:52 ` Al Viro
2019-07-07 7:56 ` Markus Elfring
2019-07-08 10:18 ` Enrico Weigelt, metux IT consult
2019-07-08 11:50 ` Markus Elfring [this message]
2019-07-08 14:38 ` Enrico Weigelt, metux IT consult
2019-07-08 6:36 ` [PATCH] " Lee Jones
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=b116fc90-9558-8609-d803-7d8da2b66e0a@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--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
all inboxes | Powered by JetHome®