linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	alexandre.belloni@bootlin.com, kavyasree.kotagiri@microchip.com,
	colin.foster@in-advantage.com, UNGLinuxDriver@microchip.com,
	maxime.chevallier@bootlin.com, michael@walle.cc,
	andy.shevchenko@gmail.com
Subject: Re: [PATCH v5 0/2] pinctrl: ocelot: Add fixes for ocelot driver
Date: Mon, 18 Jul 2022 11:23:57 +0200	[thread overview]
Message-ID: <CACRpkdawTmo2HW6kkkg=+rdCxM4EhghhgTahX+ZLKGdj8cYdmQ@mail.gmail.com> (raw)
In-Reply-To: <20220713193750.4079621-1-horatiu.vultur@microchip.com>

On Wed, Jul 13, 2022 at 9:33 PM Horatiu Vultur
<horatiu.vultur@microchip.com> wrote:

> The patch series fixes 2 issues with pincfg.
> - first issue is that on lan966x uses different offsets than sparx5
>   so it can't use directly the ocelot_confops
> - second issue is pincfg stop working when regmap support was added.

v5 applied for fixes!

Thanks for fixing this Horatiu!

Thanks to Andy for the usual first-class review as well.

Yours,
Linus Walleij

      parent reply	other threads:[~2022-07-18  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 19:37 [PATCH v5 0/2] pinctrl: ocelot: Add fixes for ocelot driver Horatiu Vultur
2022-07-13 19:37 ` [PATCH v5 1/2] pinctrl: ocelot: Fix pincfg for lan966x Horatiu Vultur
2022-07-13 19:54   ` Andy Shevchenko
2022-07-13 19:37 ` [PATCH v5 2/2] pinctrl: ocelot: Fix pincfg Horatiu Vultur
2022-07-18  9:23 ` Linus Walleij [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='CACRpkdawTmo2HW6kkkg=+rdCxM4EhghhgTahX+ZLKGdj8cYdmQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=colin.foster@in-advantage.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=michael@walle.cc \
    /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;
as well as URLs for NNTP newsgroup(s).