mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ye Zhang <ye.zhang@rock-chips.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, heiko@sntech.de,
	linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	mika.westerberg@linux.intel.com, tao.huang@rock-chips.com,
	finley.xiao@rock-chips.com, tim.chen@rock-chips.com,
	elaine.zhang@rock-chips.com
Subject: Re: [PATCH v4 3/4] gpio: rockchip: support new version GPIO
Date: Mon, 11 Nov 2024 11:48:41 +0200	[thread overview]
Message-ID: <ZzHS-cf8H-JjMkZd@smile.fi.intel.com> (raw)
In-Reply-To: <20241111023412.3466161-4-ye.zhang@rock-chips.com>

On Mon, Nov 11, 2024 at 10:34:11AM +0800, Ye Zhang wrote:
> Support the next version GPIO controller on SoCs like rk3576.

Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-11-11  9:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11  2:34 [PATCH v4 0/4] gpio: rockchip: Update the GPIO driver Ye Zhang
2024-11-11  2:34 ` [PATCH v4 1/4] gpio: rockchip: explan the format of the GPIO version ID Ye Zhang
2024-11-11  9:46   ` Andy Shevchenko
2024-11-11 22:24   ` Sebastian Reichel
2024-11-13 13:23   ` Linus Walleij
2024-11-11  2:34 ` [PATCH v4 2/4] gpio: rockchip: change the GPIO version judgment logic Ye Zhang
2024-11-11  9:48   ` Andy Shevchenko
2024-11-11 23:01   ` Sebastian Reichel
2024-11-11  2:34 ` [PATCH v4 3/4] gpio: rockchip: support new version GPIO Ye Zhang
2024-11-11  9:48   ` Andy Shevchenko [this message]
2024-11-11 22:27   ` Sebastian Reichel
2024-11-13 13:24   ` Linus Walleij
2024-11-11  2:34 ` [PATCH v4 4/4] gpio: rockchip: Set input direction when request irq Ye Zhang
2024-11-11 23:02   ` Sebastian Reichel
2024-11-13 13:25   ` Linus Walleij

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=ZzHS-cf8H-JjMkZd@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=elaine.zhang@rock-chips.com \
    --cc=finley.xiao@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tao.huang@rock-chips.com \
    --cc=tim.chen@rock-chips.com \
    --cc=ye.zhang@rock-chips.com \
    /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

all inboxes | Powered by JetHome®