[GIT PULL] Renesas intc Updates for v3.15

[GIT PULL] Renesas intc Updates for v3.15

[Simon Horman]

Hi Olof, Hi Kevin, Hi Arnd,

Please consider this Renesas ARM based SoC intc updates for v3.15.

Previously merging code for this driver was handled Paul Mundt
as part of his maintenance of SUPERH. However, SUPERH is in
the process of being orphaned. And as this driver is also listed
as being maintained by Magnus and myself as part of ARM/SHMOBILE ARM
I have picked up this patch.

If you would prefer not to handle this that is quite fine by me but in that
case I would appreciate advice on where I should send pull-requests.


The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:

  Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-intc-for-v3.15

for you to fetch changes up to 4f3068f60503e08bc9e729528d9e54289980fa96:

  sh: intc: Enable driver compilation with COMPILE_TEST (2014-02-18 09:22:21 +0900)

----------------------------------------------------------------
Renesas intc Updates for v3.15

* Enable driver compilation with COMPILE_TEST

----------------------------------------------------------------
Laurent Pinchart (1):
      sh: intc: Enable driver compilation with COMPILE_TEST

 drivers/sh/intc/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] sh: intc: Enable driver compilation with COMPILE_TEST

[Simon Horman]

From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>

This helps increasing build testing coverage.

Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 drivers/sh/intc/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/sh/intc/Kconfig b/drivers/sh/intc/Kconfig
index a305731..f7d9061 100644
--- a/drivers/sh/intc/Kconfig
+++ b/drivers/sh/intc/Kconfig
@@ -6,7 +6,7 @@ comment "Interrupt controller options"
 
 config INTC_USERIMASK
 	bool "Userspace interrupt masking support"
-	depends on ARCH_SHMOBILE || (SUPERH && CPU_SH4A)
+	depends on ARCH_SHMOBILE || (SUPERH && CPU_SH4A) || COMPILE_TEST
 	help
 	  This enables support for hardware-assisted userspace hardirq
 	  masking.
-- 
1.8.5.2

[GIT PULL] Renesas intc Updates for v3.15

[Olof Johansson]

On Fri, Feb 21, 2014 at 03:11:58PM +0900, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider this Renesas ARM based SoC intc updates for v3.15.
> 
> Previously merging code for this driver was handled Paul Mundt
> as part of his maintenance of SUPERH. However, SUPERH is in
> the process of being orphaned. And as this driver is also listed
> as being maintained by Magnus and myself as part of ARM/SHMOBILE ARM
> I have picked up this patch.
> 
> If you would prefer not to handle this that is quite fine by me but in that
> case I would appreciate advice on where I should send pull-requests.

Do you anticipate any new development besides some minor one-off fixes and
touching code that's related to shmobile/sh reworks?

If it's a low-volume thing that is likely to mostly have overlap with
arm-soc/shmobile stuff then we might just as well take most of it. Otherwise,
I think most architecture maintainers send things directly to Linus.

Either way, I'll merge this for now.


-Olof

[GIT PULL] Renesas intc Updates for v3.15

[Simon Horman]

On Sun, Mar 16, 2014 at 11:29:07PM -0700, Olof Johansson wrote:
> On Fri, Feb 21, 2014 at 03:11:58PM +0900, Simon Horman wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> > 
> > Please consider this Renesas ARM based SoC intc updates for v3.15.
> > 
> > Previously merging code for this driver was handled Paul Mundt
> > as part of his maintenance of SUPERH. However, SUPERH is in
> > the process of being orphaned. And as this driver is also listed
> > as being maintained by Magnus and myself as part of ARM/SHMOBILE ARM
> > I have picked up this patch.
> > 
> > If you would prefer not to handle this that is quite fine by me but in that
> > case I would appreciate advice on where I should send pull-requests.
> 
> Do you anticipate any new development besides some minor one-off fixes and
> touching code that's related to shmobile/sh reworks?
> 
> If it's a low-volume thing that is likely to mostly have overlap with
> arm-soc/shmobile stuff then we might just as well take most of it. Otherwise,
> I think most architecture maintainers send things directly to Linus.
> 
> Either way, I'll merge this for now.

Hi Olof,

at this stage I am not expecting major developments of drivers under
drivers/sh. But I do expect minor fixes, improvements, Kconfig updates,
etc...

I am more than happy to start sending things to Linus.
But perhaps this time it would be easiest for you to take this one.