All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Mark Salter <msalter@redhat.com>,
	Robert Richter <rrichter@marvell.com>,
	Tim Harvey <tharvey@gateworks.com>,
	Jason Cooper <jason@lakedaemon.net>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] irqchip fixes for 5.6, take #2
Date: Sat, 14 Mar 2020 10:30:00 +0000	[thread overview]
Message-ID: <20200314103000.2413-1-maz@kernel.org> (raw)

Hi Thomas,

This is hopefully the last irqchip update for 5.6. This time, a single
patch working around a hardware issue on the Cavium ThunderX and its
derivatives.

Please pull.

	M.

The following changes since commit 5186a6cc3ef5a3fa327c258924ef098b0de77006:

  irqchip/gic-v3-its: Rename VPENDBASER/VPROPBASER accessors (2020-02-08 10:01:33 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-fixes-5.6-2

for you to fetch changes up to d01fd161e85904064290435f67f4ed59af5daf74:

  irqchip/gic-v3: Workaround Cavium erratum 38539 when reading GICD_TYPER2 (2020-03-14 10:15:19 +0000)

----------------------------------------------------------------
irqchip fixes for 5.6, take #2

- Add workaround for Cavium/Marvell ThunderX unimplemented GIC registers

----------------------------------------------------------------
Marc Zyngier (1):
      irqchip/gic-v3: Workaround Cavium erratum 38539 when reading GICD_TYPER2

 Documentation/arm64/silicon-errata.rst |  2 ++
 drivers/irqchip/irq-gic-v3.c           | 30 +++++++++++++++++++++++++++++-
 2 files changed, 31 insertions(+), 1 deletion(-)

             reply	other threads:[~2020-03-15  2:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 10:30 Marc Zyngier [this message]
2020-03-15  8:48 ` [GIT PULL] irqchip fixes for 5.6, take #2 Lukas Wunner
2020-03-15 10:13   ` Marc Zyngier
2020-03-15 11:21     ` Lukas Wunner

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=20200314103000.2413-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=rrichter@marvell.com \
    --cc=tglx@linutronix.de \
    --cc=tharvey@gateworks.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.