public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, jason@lakedaemon.net,
	geert+renesas@glider.be, linux-kernel@vger.kernel.org,
	tglx@linutronix.de
Subject: Re: [PATCH 00/03] irqchip: renesas-irqc: r8a7795 and generic chip update
Date: Thu, 17 Sep 2015 16:57:21 +0900	[thread overview]
Message-ID: <20150917075721.GD5414@verge.net.au> (raw)
In-Reply-To: <20150917071230.29299.32326.sendpatchset@little-apple>

Hi Magnus,

On Thu, Sep 17, 2015 at 04:12:30PM +0900, Magnus Damm wrote:
> irqchip: renesas-irqc: r8a7795 and generic chip update
> 
> [PATCH 01/03] irqchip: renesas-irqc: Add r8a7795 IRQC DT documentation
> [PATCH 02/03] irqchip: renesas-irqc: Move over to generic chip
> [PATCH 03/03] irqchip: renesas-irqc: Enable nested lock
> 
> This series updates the IRQC driver with generic chip support including
> nested locking. Also the DT documentation is extended with r8a7795
> support.

Its not entirely clear what the relationship is between these patches
nor what the motivation is for the last two patches.

  parent reply	other threads:[~2015-09-17  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  7:12 [PATCH 00/03] irqchip: renesas-irqc: r8a7795 and generic chip update Magnus Damm
2015-09-17  7:12 ` [PATCH 01/03] irqchip: renesas-irqc: Add r8a7795 IRQC DT documentation Magnus Damm
2015-09-17  8:24   ` Geert Uytterhoeven
2015-09-17  7:12 ` [PATCH 02/03] irqchip: renesas-irqc: Move over to generic chip Magnus Damm
2015-09-17  7:12 ` [PATCH 03/03] irqchip: renesas-irqc: Enable nested lock Magnus Damm
2015-09-17  7:57 ` Simon Horman [this message]
2015-09-17  8:31   ` [PATCH 00/03] irqchip: renesas-irqc: r8a7795 and generic chip update Geert Uytterhoeven
2015-09-17 19:29     ` Laurent Pinchart
2015-09-17 22:15       ` Thomas Gleixner
2015-09-22 10:56     ` Thomas Gleixner
2015-09-28 10:50       ` Magnus Damm

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=20150917075721.GD5414@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geert+renesas@glider.be \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=tglx@linutronix.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