linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Heiko Stuebner <heiko@sntech.de>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Anson Huang <anson.huang@nxp.com>,
	Vijayakannan Ayyathurai <vijayakannan.ayyathurai@intel.com>,
	Rahul Tanwar <rtanwar@maxlinear.com>,
	Jeff LaBundy <jeff@labundy.com>, Yash Shah <yash.shah@sifive.com>,
	Sagar Kadam <sagar.kadam@sifive.com>, Vignesh R <vigneshr@ti.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH 11/15] dt-bindings: pwm: intel, keembay: do not require pwm-cells
Date: Mon, 14 Feb 2022 22:03:04 +0100	[thread overview]
Message-ID: <f9cdef5e-a52b-03ba-a069-e0bc16ccd595@canonical.com> (raw)
In-Reply-To: <20220214182824.gevtqbtv4qrddjqb@pengutronix.de>

On 14/02/2022 19:28, Uwe Kleine-König wrote:
> Hello Krzysztof,
> 
> when I read the subject line I thought the patch intention to be wrong.
> Maybe make that:
> 
> 	dt-bindings: intel,keembay-pwm: Don't require #pwm-cells twice
> 
> ?

Ah, yes, this sounds better. I'll send a v2.


Best regards,
Krzysztof

  reply	other threads:[~2022-02-14 21:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  8:15 [PATCH 01/15] dt-bindings: pwm: allwinner,sun4i-a10: include generic pwm schema Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 02/15] dt-bindings: pwm: imx: " Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 03/15] dt-bindings: pwm: intel,lgm: " Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 04/15] dt-bindings: pwm: iqs620a: " Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 05/15] dt-bindings: pwm: mxs: " Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 06/15] dt-bindings: pwm: rockchip: " Krzysztof Kozlowski
2022-02-14 10:58   ` Heiko Stübner
2022-02-14  8:15 ` [PATCH 07/15] dt-bindings: pwm: sifive: " Krzysztof Kozlowski
2022-03-11  3:14   ` Palmer Dabbelt
2022-02-14  8:15 ` [PATCH 08/15] dt-bindings: pwm: renesas,pwm: " Krzysztof Kozlowski
2022-02-14  8:15 ` [PATCH 09/15] dt-bindings: pwm: toshiba,visconti: " Krzysztof Kozlowski
2022-02-14 12:42   ` nobuhiro1.iwamatsu
2022-02-14  8:16 ` [PATCH 10/15] dt-bindings: pwm: brcm,bcm7038: do not require pwm-cells Krzysztof Kozlowski
2022-02-14 17:19   ` Florian Fainelli
2022-02-14  8:16 ` [PATCH 11/15] dt-bindings: pwm: intel,keembay: " Krzysztof Kozlowski
2022-02-14 17:54   ` Ayyathurai, Vijayakannan
2022-02-14 18:28   ` [PATCH 11/15] dt-bindings: pwm: intel, keembay: " Uwe Kleine-König
2022-02-14 21:03     ` Krzysztof Kozlowski [this message]
2022-02-14  8:16 ` [PATCH 12/15] dt-bindings: pwm: samsung: " Krzysztof Kozlowski
2022-02-14  8:16 ` [PATCH 13/15] dt-bindings: pwm: tiecap: " Krzysztof Kozlowski
2022-02-14  8:16 ` [PATCH 14/15] dt-bindings: pwm: tiehrpwm: " Krzysztof Kozlowski
2022-02-14  8:16 ` [PATCH 15/15] dt-bindings: pwm: renesas,tpu: " Krzysztof Kozlowski
2022-02-14 17:13 ` [PATCH 01/15] dt-bindings: pwm: allwinner,sun4i-a10: include generic pwm schema Jernej Škrabec

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=f9cdef5e-a52b-03ba-a069-e0bc16ccd595@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=anson.huang@nxp.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jeff@labundy.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=p.zabel@pengutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=rtanwar@maxlinear.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sagar.kadam@sifive.com \
    --cc=shawnguo@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=vigneshr@ti.com \
    --cc=vijayakannan.ayyathurai@intel.com \
    --cc=wens@csie.org \
    --cc=yash.shah@sifive.com \
    --cc=yoshihiro.shimoda.uh@renesas.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;
as well as URLs for NNTP newsgroup(s).