From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro•org>
To: "Niedermayr, BENEDIKT" <benedikt.niedermayr@siemens•com>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Cc: "rogerq@kernel•org" <rogerq@kernel•org>,
"tony@atomide•com" <tony@atomide•com>,
"krzysztof.kozlowski+dt@linaro•org"
<krzysztof.kozlowski+dt@linaro•org>,
"robh+dt@kernel•org" <robh+dt@kernel•org>
Subject: Re: [PATCH] memory: omap-gpmc: fix wait pin validation
Date: Fri, 9 Dec 2022 12:15:41 +0100 [thread overview]
Message-ID: <0898f2b3-7a75-0979-bb14-81bd802842ca@linaro.org> (raw)
In-Reply-To: <8d7b2fb49791cddc34355cdd9d7907fb8484ae7f.camel@siemens.com>
On 09/12/2022 12:10, Niedermayr, BENEDIKT wrote:
> On Fri, 2022-12-09 at 12:04 +0100, Krzysztof Kozlowski wrote:
>> On 09/12/2022 11:58, B. Niedermayr wrote:
>>> From: Benedikt Niedermayr <benedikt.niedermayr@siemens•com>
>>>
>>> This bug has been introduced after switching from -1 to UINT_MAX
>>> for GPMC_WAITPIN_INVALID.
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC. It might happen, that command when run on an older
>> kernel, gives you outdated entries. Therefore please be sure you base
>> your patches on recent Linux kernel.
>>
>> I think you got only two addresses right in your entire CC/To list...
>>
>> Please resend with correct addresses.
> OK.
>
>>
>>
>>> The bug leads to an error when the optional gpmc,wait-pin
>>> dt-property is not used:
>>>
>>> ...
>>> gpmc_cs_program_settings: invalid wait-pin (-1)
>>> ...
>>>
>>> Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens•com>
>>> Fixes: 8dd7e4af5853 ("memory: omap-gpmc: fix coverity issue "Control
>>> flow issues"")
>>> Cc: Tony Lindgren <tony@atomide•com>
>>> Cc: Rob Herring <robh+dt@kernel•org>
>>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro•org>
>>
>> Do not store maintainer entries in git log. There is no point.
>> Maintainer addresses come automatically and there is never a need to
>> keep automatic output in the history. Keep only people who need to be
>> CCed.
>>
> I wrongly thought I should Cc all people who have been Cc'ed on the
> discussion.
> Sorry, for that.
You can Cc them, that's okay, but Roger, Tony and me are maintainers, so
there is no need to store these addresses in the git log.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-12-09 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 10:58 [PATCH] memory: omap-gpmc: fix wait pin validation B. Niedermayr
2022-12-09 11:04 ` Krzysztof Kozlowski
2022-12-09 11:10 ` Niedermayr, BENEDIKT
2022-12-09 11:15 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 12:31 B. Niedermayr
2022-12-12 7:16 ` Tony Lindgren
2022-12-12 9:08 ` Roger Quadros
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=0898f2b3-7a75-0979-bb14-81bd802842ca@linaro.org \
--to=krzysztof.kozlowski@linaro$(echo .)org \
--cc=benedikt.niedermayr@siemens$(echo .)com \
--cc=krzysztof.kozlowski+dt@linaro$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robh+dt@kernel$(echo .)org \
--cc=rogerq@kernel$(echo .)org \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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