From: Roger Quadros <rogerq@kernel•org>
To: "B. Niedermayr" <benedikt.niedermayr@siemens•com>,
linux-next@vger•kernel.org, Tony Lindgren <tony@atomide•com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro•org>
Cc: Rob Herring <robh+dt@kernel•org>,
"open list:OMAP GENERAL PURPOSE MEMORY CONTROLLER SUPPORT"
<linux-omap@vger•kernel.org>,
"open list:MEMORY CONTROLLER DRIVERS"
<linux-kernel@vger•kernel.org>
Subject: Re: [PATCH] memory: omap-gpmc: fix wait pin validation
Date: Mon, 12 Dec 2022 11:08:47 +0200 [thread overview]
Message-ID: <0a42d725-ce95-216f-6078-877590be1d09@kernel.org> (raw)
In-Reply-To: <20221209123147.591982-1-benedikt.niedermayr@siemens.com>
On 09/12/2022 14:31, 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.
>
> 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: Rob Herring <robh+dt@kernel•org>
Acked-by: Roger Quadros <rogerq@kernel•org>
next prev parent reply other threads:[~2022-12-12 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 12:31 [PATCH] memory: omap-gpmc: fix wait pin validation B. Niedermayr
2022-12-12 7:16 ` Tony Lindgren
2022-12-12 9:08 ` Roger Quadros [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 10:58 B. Niedermayr
2022-12-09 11:04 ` Krzysztof Kozlowski
2022-12-09 11:10 ` Niedermayr, BENEDIKT
2022-12-09 11:15 ` Krzysztof Kozlowski
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=0a42d725-ce95-216f-6078-877590be1d09@kernel.org \
--to=rogerq@kernel$(echo .)org \
--cc=benedikt.niedermayr@siemens$(echo .)com \
--cc=krzysztof.kozlowski@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=robh+dt@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