public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide•com>
To: Drew Fustini <drew@beagleboard•org>
Cc: Grygorii Strashko <grygorii.strashko@ti•com>,
	Linus Walleij <linus.walleij@linaro•org>,
	linux-kernel@vger•kernel.org,
	Robert Nelson <robertcnelson@beagleboard•org>,
	linux-gpio@vger•kernel.org,
	Jason Kridner <jkridner@beagleboard•org>,
	Haojian Zhuang <haojian.zhuang@linaro•org>,
	linux-omap@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v2] pinctrl-single: fix pcs_parse_pinconf() return value
Date: Tue, 9 Jun 2020 11:06:31 -0700	[thread overview]
Message-ID: <20200609180631.GS37466@atomide.com> (raw)
In-Reply-To: <20200608125143.GA2789203@x1>

* Drew Fustini <drew@beagleboard•org> [200608 12:52]:
> This patch causes pcs_parse_pinconf() to return -ENOTSUPP when no
> pinctrl_map is added.  The current behavior is to return 0 when
> !PCS_HAS_PINCONF or !nconfs.  Thus pcs_parse_one_pinctrl_entry()
> incorrectly assumes that a map was added and sets num_maps = 2.
...

> Fixes: 9dddb4df90d1 ("pinctrl: single: support generic pinconf")

It would be good to get an ack/tested-by from Haojian for this.

The patch looks right to me:

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-06-09 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 12:51 [PATCH v2] pinctrl-single: fix pcs_parse_pinconf() return value Drew Fustini
2020-06-09 18:06 ` Tony Lindgren [this message]
2020-06-16  8:31 ` Linus Walleij
2020-06-16 11:59   ` Drew Fustini
2020-06-26 19:19     ` Drew Fustini
2020-07-05  8:58 ` Haojian Zhuang

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=20200609180631.GS37466@atomide.com \
    --to=tony@atomide$(echo .)com \
    --cc=drew@beagleboard$(echo .)org \
    --cc=grygorii.strashko@ti$(echo .)com \
    --cc=haojian.zhuang@linaro$(echo .)org \
    --cc=jkridner@beagleboard$(echo .)org \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-omap@vger$(echo .)kernel.org \
    --cc=robertcnelson@beagleboard$(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