public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide•com>
To: "B. Niedermayr" <benedikt.niedermayr@siemens•com>
Cc: linux-next@vger•kernel.org, Roger Quadros <rogerq@kernel•org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro•org>,
	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 09:16:17 +0200	[thread overview]
Message-ID: <Y5bVQSfFV+luA6T0@atomide.com> (raw)
In-Reply-To: <20221209123147.591982-1-benedikt.niedermayr@siemens.com>

* B. Niedermayr <benedikt.niedermayr@siemens•com> [221209 12:32]:
> 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)
> ...

This fixes the issue thanks:

Tested-by: Tony Lindgren <tony@atomide•com>

  reply	other threads:[~2022-12-12  7:16 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 [this message]
2022-12-12  9:08 ` Roger Quadros
  -- 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=Y5bVQSfFV+luA6T0@atomide.com \
    --to=tony@atomide$(echo .)com \
    --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=rogerq@kernel$(echo .)org \
    /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