public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"pi-cheng.chen" <pi-cheng.chen@linaro.org>,
	Alexei Starovoitov <ast@plumgrid.com>,
	Markus Pargmann <mpa@pengutronix.de>
Subject: Re: linux-next: Tree for Aug 31 (new arm, arm64, s390 failures)
Date: Mon, 31 Aug 2015 21:07:32 +0100	[thread overview]
Message-ID: <20150831200732.GT5313@sirena.org.uk> (raw)
In-Reply-To: <20150831192657.557e45cc@why.wild-wind.fr.eu.org>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

On Mon, Aug 31, 2015 at 07:26:57PM +0100, Marc Zyngier wrote:

> which never considers bus to be NULL in __regmap_init. With the
> following patch applied, I can boot to a prompt:
> 
> From 031eae5a1b34f952ba3dcaecb4eb4ec9d3bda352 Mon Sep 17 00:00:00 2001

> From: Marc Zyngier <marc.zyngier@arm.com>
> Date: Mon, 31 Aug 2015 19:16:16 +0100
> Subject: [PATCH] regmap: Fix max_raw_read/write handling when bus is NULL

Please submit patches using the process documented in SubmittingPatches,
don't bury them in the middle of a reply to some random other thread
where they can't be applied without handholding :(

> -	map->max_raw_read = bus->max_raw_read;
> -	map->max_raw_write = bus->max_raw_write;
> +	map->max_raw_read = bus ? bus->max_raw_read : 0;
> +	map->max_raw_write = bus ? bus->max_raw_write : 0;

A more legible version of this patch was already applied.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-08-31 20:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  9:54 linux-next: Tree for Aug 31 Stephen Rothwell
2015-08-31 14:17 ` linux-next: Tree for Aug 31 (new arm, arm64, s390 failures) Guenter Roeck
2015-08-31 15:09   ` Alexei Starovoitov
2015-08-31 15:31   ` Marc Zyngier
2015-08-31 15:47     ` Guenter Roeck
2015-08-31 16:18       ` Marc Zyngier
2015-08-31 16:40         ` Guenter Roeck
2015-08-31 17:09           ` Marc Zyngier
2015-08-31 18:26             ` Marc Zyngier
2015-08-31 18:57               ` Guenter Roeck
2015-08-31 19:13                 ` Marc Zyngier
2015-08-31 19:40                   ` Guenter Roeck
2015-08-31 20:07               ` Mark Brown [this message]
2015-08-31 18:33             ` Guenter Roeck

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=20150831200732.GT5313@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ast@plumgrid.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marc.zyngier@arm.com \
    --cc=mpa@pengutronix.de \
    --cc=pi-cheng.chen@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /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