From: Magnus Damm <magnus.damm@gmail.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 09/09] Random build workarounds for renesas-drivers
Date: Wed, 19 Dec 2018 19:27:30 +0900 [thread overview]
Message-ID: <154521525038.7290.12170153110718373437.sendpatchset@octo> (raw)
In-Reply-To: <154521516632.7290.5245227863765109428.sendpatchset@octo>
From: Magnus Damm <damm+renesas@opensource.se>
The latest renesas-drivers release does not build for me with
the arm64 defconfig. Probably related to my old toolchain.
Take the easy way out and work around the build issues locally.
Not for upstream merge.
Not-Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---
Applies on top of renesas-drivers-2018-12-18-v4.20-rc7
arch/arm64/include/asm/smp.h | 2 +-
drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 2 +-
drivers/tty/serial/sh-sci.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--- 0001/arch/arm64/include/asm/smp.h
+++ work/arch/arm64/include/asm/smp.h 2018-12-19 13:51:47.246815997 +0900
@@ -30,7 +30,7 @@
#define CPU_PANIC_KERNEL (3)
#define CPU_STUCK_REASON_52_BIT_VA (1U << CPU_STUCK_REASON_SHIFT)
-#define CPU_STUCK_REASON_NO_GRAN (2U << CPU_STUCK_REASON_SHIFT)
+#define CPU_STUCK_REASON_NO_GRAN (2 << CPU_STUCK_REASON_SHIFT)
#ifndef __ASSEMBLY__
--- 0001/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c
+++ work/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c 2018-12-19 14:06:48.699077685 +0900
@@ -560,7 +560,7 @@ dw_mipi_dsi_get_lane_mbps(void *priv_dat
static const struct dw_mipi_dsi_phy_ops dw_mipi_dsi_rockchip_phy_ops = {
.init = dw_mipi_dsi_phy_init,
- .get_lane_mbps = dw_mipi_dsi_get_lane_mbps,
+ //.get_lane_mbps = dw_mipi_dsi_get_lane_mbps,
};
static void dw_mipi_dsi_rockchip_config(struct dw_mipi_dsi_rockchip *dsi,
--- 0001/drivers/tty/serial/sh-sci.c
+++ work/drivers/tty/serial/sh-sci.c 2018-12-19 13:42:38.328037070 +0900
@@ -1347,7 +1347,7 @@ static int sci_submit_rx(struct sci_port
{
struct dma_chan *chan = s->chan_rx;
struct uart_port *port = &s->port;
- unsigned long flags;
+ unsigned long flags = 0;
int i;
for (i = 0; i < 2; i++) {
prev parent reply other threads:[~2018-12-19 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 10:26 [PATCH 00/09] Test R-Car Gen3 IMR-LX4 device Magnus Damm
2018-12-19 10:26 ` [PATCH 01/09] Prototype code for basic IMR-LX4 test Magnus Damm
2018-12-19 10:26 ` [PATCH 02/09] arm64: dts: renesas: r8a7795: One IMR-LX4 device for R-Car H3 Magnus Damm
2018-12-19 10:26 ` [PATCH 03/09] arm64: dts: renesas: r8a7796: One IMR-LX4 device for R-Car M3-W Magnus Damm
2018-12-19 10:26 ` [PATCH 04/09] arm64: dts: renesas: r8a77965: One IMR-LX4 device for R-Car M3-N Magnus Damm
2018-12-19 10:26 ` [PATCH 05/09] arm64: dts: renesas: r8a77970: One IMR-LX4 device for R-Car V3M Magnus Damm
2018-12-19 10:27 ` [PATCH 06/09] arm64: dts: renesas: r8a77980: One IMR-LX4 device for R-Car V3H Magnus Damm
2018-12-19 10:27 ` [PATCH 07/09] arm64: dts: renesas: r8a77995: One IMR-LX4 device for R-Car D3 Magnus Damm
2018-12-19 10:27 ` [PATCH 08/09] arm64: dts: renesas: r8a77990: One IMR-LX4 device for R-Car E3 Magnus Damm
2018-12-19 10:27 ` Magnus Damm [this message]
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=154521525038.7290.12170153110718373437.sendpatchset@octo \
--to=magnus.damm@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).