All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Timo Alho <talho@nvidia.com>,
	treding@nvidia.com, sivaramn@nvidia.com, robh@kernel.org
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V3 2/4] firmware: tegra: refactor bpmp driver
Date: Thu, 24 Jan 2019 18:24:45 +0000	[thread overview]
Message-ID: <817c0a76-4eda-4f66-e3d4-fee7b4583cf1@nvidia.com> (raw)
In-Reply-To: <1548349435-1086-3-git-send-email-talho@nvidia.com>


On 24/01/2019 17:03, Timo Alho wrote:
> Split bpmp driver into common and chip specific parts to facilitate
> adding support for previous and future Tegra chips that are using bpmp
> as co-processor.
> 
> Signed-off-by: Timo Alho <talho@nvidia.com>
Acked-by: Jon Hunter <jonathanh@nvidia.com>

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2019-01-24 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 17:03 [PATCH V3 0/4] add Tegra210 BPMP driver Timo Alho
2019-01-24 17:03 ` [PATCH V3 1/4] firmware: tegra: reword messaging terminology Timo Alho
2019-01-24 17:03 ` [PATCH V3 2/4] firmware: tegra: refactor bpmp driver Timo Alho
2019-01-24 18:24   ` Jon Hunter [this message]
2019-01-24 17:03 ` [PATCH V3 3/4] firmware: tegra: add bpmp driver for Tegra210 Timo Alho
2019-01-25 13:34   ` Jon Hunter
2019-01-24 17:03 ` [PATCH V3 4/4] dt-bindings: firmware: Add bindings for Tegra210 BPMP Timo Alho
2019-01-24 18:29   ` Jon Hunter
2019-01-24 18:40     ` Timo Alho
2019-01-25 14:57 ` [PATCH V3 0/4] add Tegra210 BPMP driver 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=817c0a76-4eda-4f66-e3d4-fee7b4583cf1@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sivaramn@nvidia.com \
    --cc=talho@nvidia.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.