mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] reset: tegra: Changes for v4.15-rc1
Date: Fri, 20 Oct 2017 14:17:01 +0200	[thread overview]
Message-ID: <20171020121701.10873-1-thierry.reding@gmail.com> (raw)

Hi Philipp,

The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:

  Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.15-reset

for you to fetch changes up to cfbf86684733d4501230ff4efdeb3225599df78b:

  reset: tegra: Check BPMP response return code (2017-10-19 16:40:54 +0200)

Note that this pulls in part of the tegra-for-4.15-firmware tag that is
going in via the ARM SoC tree. This is needed to resolve a build time
dependency as discussed earlier on the mailing list.

Thanks,
Thierry

----------------------------------------------------------------
reset: tegra: Changes for v4.15-rc1

Contains a fix to properly handle errors propagated by the BPMP.

----------------------------------------------------------------
Thierry Reding (1):
      Merge branch 'for-4.15/firmware' into for-4.15/reset

Timo Alho (2):
      firmware: tegra: Propagate error code to caller
      reset: tegra: Check BPMP response return code

 drivers/firmware/tegra/bpmp.c    | 22 ++++++++++++++++------
 drivers/reset/tegra/reset-bpmp.c |  9 ++++++++-
 include/soc/tegra/bpmp.h         |  1 +
 3 files changed, 25 insertions(+), 7 deletions(-)

                 reply	other threads:[~2017-10-20 12:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171020121701.10873-1-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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
Powered by JetHome