From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Chanwoo Choi <cw00.choi@samsung.com>, kernel-janitors@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: extcon: max14577: Use common error handling code in max14577_muic_set_path()
Date: Mon, 23 Oct 2017 08:08:43 +0200 [thread overview]
Message-ID: <d0cc81a4-6301-13ee-1589-e8a95813f106@users.sourceforge.net> (raw)
In-Reply-To: <59ED8639.7020605@samsung.com>
>>> I think that there is any benefit of this patch.
>>> Also, as I commented, it make the code more complicated.
>>
>> We have got different software development opinions about
>
> I agree absolutely. So, anyone can suggest the opinion and send patches.
> But, all patches have to get the review from maintainer, reviewer
> or the mailing-list developer.
Can an other change acceptance evolve over time?
> (Please don't remove the part of my comment when you reply.)
>
>> the shown change possibilities then.
Do you find similar updates more useful for any other software modules?
Regards,
Markus
prev parent reply other threads:[~2017-10-23 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d08cbbf6-015a-ab76-6491-126901d1dda6@users.sourceforge.net>
[not found] ` <5cdefd84-066d-5379-43c8-76f5d3b8f7c4@users.sourceforge.net>
[not found] ` <20171022185941.mzplggaick742ylf@kozik-lap>
2017-10-22 20:15 ` [PATCH 1/2] extcon: max14577: Use common error handling code in max14577_muic_set_path() SF Markus Elfring
[not found] ` <59ED3E72.7010401@samsung.com>
2017-10-23 5:45 ` SF Markus Elfring
2017-10-23 5:54 ` Chanwoo Choi
2017-10-23 5:57 ` SF Markus Elfring
2017-10-23 6:03 ` Chanwoo Choi
2017-10-23 6:08 ` SF Markus Elfring [this message]
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=d0cc81a4-6301-13ee-1589-e8a95813f106@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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