From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: treding@nvidia.com, linux-tegra@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v4 1/2] firmware: tegra: Update BPMP ABI
Date: Tue, 01 Nov 2022 11:19:02 -0700 [thread overview]
Message-ID: <20221101181904.C556DC433D6@smtp.kernel.org> (raw)
In-Reply-To: <Y1u51EiIc3LEGgV1@orome>
Quoting Thierry Reding (2022-10-28 04:15:32)
> On Thu, Oct 27, 2022 at 03:13:53PM +0300, Peter De Schrijver wrote:
> > Update the BPMP ABI to align with the the latest version.
> >
> > Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> > ---
> > include/soc/tegra/bpmp-abi.h | 1802 +++++++++++++++++++++++++---------
> > 1 file changed, 1357 insertions(+), 445 deletions(-)
>
> Looks good to me.
>
> Mike, Stephen, do you have any objections if I pick these two patches up
> into the Tegra tree to manage the dependencies? There's another patch
> that will need some of the BPMP ABI additions added here which we may
> get ready in time for v6.2, so it'd be good to have this in a shared
> branch.
>
> I don't think it'll be necessary for me to pick any other clock driver
> changes, though, as long as they don't conflict with these BPMP clock
> driver changes. But if you prefer, I can collect others as well and send
> them all your way later on in the release cycle.
It is fine to take them through your tree.
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2022-11-01 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 12:13 [PATCH v4 1/2] firmware: tegra: Update BPMP ABI Peter De Schrijver
2022-10-27 12:13 ` [PATCH v4 2/2] clk: tegra: support BPMP-FW ABI deny flags Peter De Schrijver
2022-10-28 11:15 ` [PATCH v4 1/2] firmware: tegra: Update BPMP ABI Thierry Reding
2022-11-01 18:19 ` Stephen Boyd [this message]
2022-11-17 22:37 ` Thierry Reding
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=20221101181904.C556DC433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.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.