From: Yisheng Xie <xieyisheng1@huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB <linux-usb@vger.kernel.org>, Felipe Balbi <balbi@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 01/21] usb: phy: use match_string() helper
Date: Tue, 5 Jun 2018 17:28:32 +0800 [thread overview]
Message-ID: <4ea021ae-1284-4519-e467-5c03bc62c98b@huawei.com> (raw)
In-Reply-To: <CAHp75VfUvcCJEyisNG0cgiL8GCdNQvSaefJVW2yx7HWDHC45cw@mail.gmail.com>
On 2018/6/1 2:59, Andy Shevchenko wrote:
> On Thu, May 31, 2018 at 9:56 PM, Sergei Shtylyov
> <sergei.shtylyov@cogentembedded.com> wrote:
>> On 05/31/2018 09:47 PM, Andy Shevchenko wrote:
>
>>>>> - int err, i;
>
>>>>> + err = match_string(usbphy_modes, ARRAY_SIZE(usbphy_modes), phy_type);
>>>>> + if (err < 0)
>>>>
>>>> This is one of the few cases when 'err' is not the best name for such a
>>>> variable. I'd prefer to see something like 'match' or even 'rc' or 'ret'... :-)
>>>
>>> Then leaving i would make it?
>> Yes. :-)
>
> So, I leave it to Greg to decide either it's okay in this version, or
> needs update with i left untouched.
Hi Greg,
IIRC, you seems want to keep the err unchanged, right?
Please let me know if another version is need.
Thanks
Yisheng
>
>>> I'm okay with either which just not renames err, b/c it's used with
>>> something else in this function.
>>
>> Looking at it again, 'err' seems equally bad for the result of
>> of_property_read_string()... unless the check there is changed to just *if* (err) --
>> this function never returns positive values, 0 means success, others mean error.
>
> While you seems right, this is matter of another change which you are
> welcome to propose.
>
next prev parent reply other threads:[~2018-06-05 9:29 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 11:11 [PATCH v2 00/21] " Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 01/21] usb: phy: " Yisheng Xie
2018-05-31 16:55 ` Sergei Shtylyov
2018-05-31 18:47 ` Andy Shevchenko
2018-05-31 18:56 ` Sergei Shtylyov
2018-05-31 18:59 ` Andy Shevchenko
2018-06-05 9:28 ` Yisheng Xie [this message]
2018-05-31 11:11 ` [PATCH v2 02/21] mfd: omap-usb-host: " Yisheng Xie
2018-06-04 7:44 ` Lee Jones
2018-06-04 8:13 ` Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 03/21] Staging: gdm724x: " Yisheng Xie
2018-05-31 11:44 ` Greg Kroah-Hartman
2018-05-31 12:12 ` Yisheng Xie
2018-06-06 2:21 ` [PATCH v3 " Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 04/21] cxgb4: " Yisheng Xie
2018-06-05 13:19 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 05/21] hp100: " Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 06/21] iwlwifi: mvm: " Yisheng Xie
2018-06-05 13:19 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 07/21] bus: fsl-mc: " Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 08/21] clk: bcm2835: " Yisheng Xie
2018-06-02 6:17 ` Stephen Boyd
2018-05-31 11:11 ` [PATCH v2 09/21] clk: " Yisheng Xie
2018-06-02 6:17 ` Stephen Boyd
2018-05-31 11:11 ` [PATCH v2 10/21] cpufreq: intel_pstate: " Yisheng Xie
2018-06-26 15:23 ` Rafael J. Wysocki
2018-06-26 23:56 ` Srinivas Pandruvada
2018-07-04 10:52 ` Rafael J. Wysocki
2018-05-31 11:11 ` [PATCH v2 11/21] drm/nouveau: " Yisheng Xie
2018-06-05 13:20 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 12/21] drm: i2c: ch7006: " Yisheng Xie
2018-06-05 13:21 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 13/21] ima: " Yisheng Xie
2018-05-31 15:02 ` Mimi Zohar
2018-06-01 10:55 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 14/21] sched/debug: " Yisheng Xie
2018-06-05 13:21 ` Andy Shevchenko
2018-05-31 11:11 ` [PATCH v2 15/21] ALSA: oxygen: " Yisheng Xie
2018-05-31 18:39 ` Takashi Iwai
2018-05-31 18:40 ` Andy Shevchenko
2018-05-31 18:43 ` Takashi Iwai
2018-05-31 18:44 ` Andy Shevchenko
2018-05-31 18:41 ` Andy Shevchenko
2018-05-31 18:59 ` Takashi Iwai
2018-05-31 19:02 ` Andy Shevchenko
2018-05-31 20:30 ` Takashi Iwai
2018-05-31 11:11 ` [PATCH v2 16/21] ASoC: max98088: " Yisheng Xie
2018-05-31 11:49 ` Mark Brown
2018-05-31 12:25 ` Yisheng Xie
2018-05-31 16:02 ` Mark Brown
2018-06-01 0:38 ` Yisheng Xie
2018-05-31 16:09 ` Applied "ASoC: max98088: use match_string() helper" to the asoc tree Mark Brown
2018-05-31 11:11 ` [PATCH v2 17/21] ASoC: max98095: use match_string() helper Yisheng Xie
2018-05-31 16:09 ` Applied "ASoC: max98095: use match_string() helper" to the asoc tree Mark Brown
2018-05-31 11:11 ` [PATCH v2 18/21] ASoC: dapm: use match_string() helper Yisheng Xie
2018-05-31 11:11 ` [PATCH v2 19/21] bcache: " Yisheng Xie
2018-06-01 3:45 ` Coly Li
2018-06-01 4:32 ` Yisheng Xie
2018-06-01 5:04 ` Coly Li
2018-05-31 11:11 ` [PATCH v2 20/21] powerpc/xmon: " Yisheng Xie
2018-06-04 14:11 ` [v2,20/21] " Michael Ellerman
2018-05-31 11:11 ` [PATCH v2 21/21] sparc64: " Yisheng Xie
2018-06-01 11:34 ` Andy Shevchenko
2018-06-04 1:06 ` Yisheng Xie
2018-06-04 10:06 ` Andy Shevchenko
2018-06-05 9:05 ` Yisheng Xie
2018-06-06 2:19 ` [PATCH v3 " Yisheng Xie
2018-06-06 5:01 ` Andy Shevchenko
2018-06-21 1:13 ` Yisheng Xie
2018-06-21 1:39 ` [PATCH v4 " Yisheng Xie
2018-06-21 2:24 ` Andy Shevchenko
2018-05-31 12:23 ` [PATCH v2 00/21] " Yisheng Xie
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=4ea021ae-1284-4519-e467-5c03bc62c98b@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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
Powered by JetHome