All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: cip-dev@lists.cip-project.org,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Pavel Machek <pavel@denx.de>,
	Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Subject: Re: [PATCH 6.1.y-cip 0/6]  Add RZ/{G2L,G2LC,V2L} MTU3 PWM support.
Date: Wed, 19 Jul 2023 16:11:12 +0200	[thread overview]
Message-ID: <ZLfvACwmys4CMRdk@duo.ucw.cz> (raw)
In-Reply-To: <20230718141129.119809-1-biju.das.jz@bp.renesas.com>

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

Hi!

> This patch series aims to add support for RZ/{G2L,G2LC,V2L}
> MTU3 PWM driver.
> 
> All the patches are cherry-picked from the mainline
> except patch#4-patch#6. The trivial patches#4-#6 are
> cherry-picked from next.

So... this is similar to 5.10, and same comments apply except that
WARN_ON. They are details that should not block merge.

But we really should not be merging patches that are not yet upstream
(because policy and because the commit numbers would change).

So I'd propose testing this and then merging all the patches that are
mainline (for both this and 5.10 series), unless there are other
comments.

Thanks and best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2023-07-19 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 14:11 [PATCH 6.1.y-cip 0/6] Add RZ/{G2L,G2LC,V2L} MTU3 PWM support Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 1/6] arm64: dts: renesas: rzg2lc-smarc: Include SoM DTSI into board DTS Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 2/6] arm64: defconfig: Enable Renesas MTU3a counter config Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 3/6] pwm: Add Renesas RZ/G2L MTU3a PWM driver Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 4/6] arm64: dts: renesas: rzg2l-smarc: Add support for enabling MTU3 Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 5/6] arm64: dts: renesas: rzg2lc-smarc: " Biju Das
2023-07-18 14:11 ` [PATCH 6.1.y-cip 6/6] arm64: defconfig: Enable Renesas MTU3a PWM config Biju Das
2023-07-19 14:11 ` Pavel Machek [this message]
2023-07-20  9:59 ` [PATCH 6.1.y-cip 0/6] Add RZ/{G2L,G2LC,V2L} MTU3 PWM support nobuhiro1.iwamatsu
2023-07-20 11:05   ` Biju Das
2023-07-20 11:33   ` Pavel Machek

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=ZLfvACwmys4CMRdk@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=fabrizio.castro.jz@renesas.com \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.