All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
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
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>
Subject: Re: [PATCH v4 0/3] clk: zynqmp: Add firmware specific clock flags
Date: Tue, 22 Sep 2020 13:07:08 -0700	[thread overview]
Message-ID: <160080522837.310579.7160115709529621594@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1599684288-20917-1-git-send-email-amit.sunil.dhamne@xilinx.com>

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.
> 
> Changes in v4:
>  - Use if condition instead of ternary operator.
> 

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.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
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
Cc: Amit Sunil Dhamne <amit.sunil.dhamne@xilinx.com>,
	tejasp@xilinx.com, linux-kernel@vger.kernel.org,
	jollys@xilinx.com, rajanv@xilinx.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] clk: zynqmp: Add firmware specific clock flags
Date: Tue, 22 Sep 2020 13:07:08 -0700	[thread overview]
Message-ID: <160080522837.310579.7160115709529621594@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <1599684288-20917-1-git-send-email-amit.sunil.dhamne@xilinx.com>

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.
> 
> Changes in v4:
>  - Use if condition instead of ternary operator.
> 

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.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-09-22 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 20:44 [PATCH v4 0/3] clk: zynqmp: Add firmware specific clock flags Amit Sunil Dhamne
2020-09-09 20:44 ` Amit Sunil Dhamne
2020-09-09 20:44 ` [PATCH v4 1/3] clk: zynqmp: Use firmware specific common " Amit Sunil Dhamne
2020-09-09 20:44   ` Amit Sunil Dhamne
2020-09-09 20:44 ` [PATCH v4 2/3] clk: zynqmp: Use firmware specific divider " Amit Sunil Dhamne
2020-09-09 20:44   ` Amit Sunil Dhamne
2020-09-09 20:44 ` [PATCH v4 3/3] clk: zynqmp: Use firmware specific mux " Amit Sunil Dhamne
2020-09-09 20:44   ` Amit Sunil Dhamne
2020-09-22 20:07 ` Stephen Boyd [this message]
2020-09-22 20:07   ` [PATCH v4 0/3] clk: zynqmp: Add firmware specific " Stephen Boyd

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=160080522837.310579.7160115709529621594@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=amit.sunil.dhamne@xilinx.com \
    --cc=jollys@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.tretter@pengutronix.de \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=mturquette@baylibre.com \
    --cc=rajanv@xilinx.com \
    --cc=tejasp@xilinx.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 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.