Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: ye.xingchen@zte.com.cn, lee@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	chi.minghao@zte.com.cn
Subject: Re: [PATCH] mfd: exynos-lpass: use devm_platform_get_and_ioremap_resource()
Date: Fri, 11 Nov 2022 10:54:23 +0100	[thread overview]
Message-ID: <94e1fffd-a28e-48aa-26b7-3d96c54bedc7@linaro.org> (raw)
In-Reply-To: <202211111640089246472@zte.com.cn>

On 11/11/2022 09:40, ye.xingchen@zte.com.cn wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
> 
> Convert platform_get_resource(), devm_ioremap_resource() to a single
> call to devm_platform_get_and_ioremap_resource(), as this is exactly
> what this function does.
> 
> Reported-by: Zeal Robot <zealci@zte.com.cn>

1. I cannot find this report. This is an open source work and public
collaboration. The "Reported-by" usually means that the issue was
reported to us, in some way, usually in public. Can we see the report?
Otherwise adding non-public, non-verifiable reports is useless and
clutters our report-credit-system.

2. Where is the bug? Reported-by means there was a bug being fixed.
Please describe the visible effects of bug and its impact.

Otherwise please stop adding bogus reported-by messages. I have seen to
many bogus reported-by tags from ZTE last months.

> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> ---
>  drivers/mfd/exynos-lpass.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)

Best regards,
Krzysztof


      reply	other threads:[~2022-11-11  9:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  8:40 [PATCH] mfd: exynos-lpass: use devm_platform_get_and_ioremap_resource() ye.xingchen
2022-11-11  9:54 ` Krzysztof Kozlowski [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=94e1fffd-a28e-48aa-26b7-3d96c54bedc7@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=chi.minghao@zte.com.cn \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=ye.xingchen@zte.com.cn \
    /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