From: Olof Johansson <olof@lixom.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas intc Updates for v3.15
Date: Mon, 17 Mar 2014 06:29:07 +0000 [thread overview]
Message-ID: <20140317062907.GA21917@quad.lixom.net> (raw)
In-Reply-To: <cover.1392962498.git.horms+renesas@verge.net.au>
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
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas intc Updates for v3.15
Date: Sun, 16 Mar 2014 23:29:07 -0700 [thread overview]
Message-ID: <20140317062907.GA21917@quad.lixom.net> (raw)
In-Reply-To: <cover.1392962498.git.horms+renesas@verge.net.au>
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
next prev parent reply other threads:[~2014-03-17 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:11 [GIT PULL] Renesas intc Updates for v3.15 Simon Horman
2014-02-21 6:11 ` Simon Horman
2014-02-21 6:12 ` [PATCH] sh: intc: Enable driver compilation with COMPILE_TEST Simon Horman
2014-02-21 6:12 ` Simon Horman
2014-03-17 6:29 ` Olof Johansson [this message]
2014-03-17 6:29 ` [GIT PULL] Renesas intc Updates for v3.15 Olof Johansson
2014-03-17 6:52 ` Simon Horman
2014-03-17 6:52 ` Simon Horman
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=20140317062907.GA21917@quad.lixom.net \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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 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.