Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1599684288-20917-1-git-send-email-amit.sunil.dhamne@xilinx.com>
References: <1599684288-20917-1-git-send-email-amit.sunil.dhamne@xilinx.com>
Subject: Re: [PATCH v4 0/3] clk: zynqmp: Add firmware specific clock flags
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     rajanv@xilinx.com, jollys@xilinx.com, tejasp@xilinx.com,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>
To:     Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>,
        linux-clk@vger.kernel.org, m.tretter@pengutronix.de,
        mark.rutland@arm.com, michal.simek@xilinx.com,
        mturquette@baylibre.com
Date:   Tue, 22 Sep 2020 13:07:08 -0700
Message-ID: <160080522837.310579.7160115709529621594@swboyd.mtv.corp.google.com>
User-Agent: alot/0.9.1
Precedence: bulk

Quoting Amit Sunil Dhamne (2020-09-09 13:44:45)
> Currently firmware is maintaining CCF specific flags and provides to
> CCF as it is. But CCF flag numbers may change and that shouldn't mean
> that the firmware needs to change. The firmware should have its own
> 'flag number space' that is distinct from the common clk framework's
> 'flag number space'. So use firmware specific clock flags in ZynqMP
> clock driver instead of CCF flags.
>=20
> Changes in v4:
>  - Use if condition instead of ternary operator.
>=20

Thanks. This patch series doesn't apply for me though. What is the base
of the patches? Can you use the --base option when formatting patches
with git format-patch? That would help me.

Also, I think your MUA or SMTP server is mangling the format. I had
trouble trying to apply the patches from my local copy so I had to
fallback to lore but even that didn't work.

Please resend.