From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] irqdomain: protect macro variable in domain iterators
Date: Thu, 08 Dec 2011 07:30:11 -0600 [thread overview]
Message-ID: <4EE0BBE3.60508@gmail.com> (raw)
In-Reply-To: <4EE08569.3070009@atmel.com>
On 12/08/2011 03:37 AM, Nicolas Ferre wrote:
> On 12/02/2011 02:44 PM, Dave Martin :
>> On Fri, Dec 02, 2011 at 02:30:09PM +0100, Nicolas Ferre wrote:
>>> Signed-off-by: Nicolas Ferre<nicolas.ferre@atmel.com>
>>
>> Looks OK to me:
>>
>> Acked-by: Dave Martin<dave.martin@linaro.org>
>
> Rob,
>
> Do you want a different implementation for this. I think it is the
> simplest way to write this macro...
>
> If it is ok for you, it will be interesting to include this patch
> quickly so that I will be able to queue my own patches on top of it.
> (Cc: stable can be a good idea also).
>
Yes, it's fine. The irqdomain patches need to be taken by tglx or acked
by him. I don't think this is needed for stable. The existing users are
fine and new ones aren't going to be added to stable kernels.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
Dave Martin <dave.martin@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] irqdomain: protect macro variable in domain iterators
Date: Thu, 08 Dec 2011 07:30:11 -0600 [thread overview]
Message-ID: <4EE0BBE3.60508@gmail.com> (raw)
In-Reply-To: <4EE08569.3070009@atmel.com>
On 12/08/2011 03:37 AM, Nicolas Ferre wrote:
> On 12/02/2011 02:44 PM, Dave Martin :
>> On Fri, Dec 02, 2011 at 02:30:09PM +0100, Nicolas Ferre wrote:
>>> Signed-off-by: Nicolas Ferre<nicolas.ferre@atmel.com>
>>
>> Looks OK to me:
>>
>> Acked-by: Dave Martin<dave.martin@linaro.org>
>
> Rob,
>
> Do you want a different implementation for this. I think it is the
> simplest way to write this macro...
>
> If it is ok for you, it will be interesting to include this patch
> quickly so that I will be able to queue my own patches on top of it.
> (Cc: stable can be a good idea also).
>
Yes, it's fine. The irqdomain patches need to be taken by tglx or acked
by him. I don't think this is needed for stable. The existing users are
fine and new ones aren't going to be added to stable kernels.
Rob
next prev parent reply other threads:[~2011-12-08 13:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 13:53 [PATCH] irqdomain: protect macro variable in domain iterators Nicolas Ferre
2011-12-02 13:53 ` Nicolas Ferre
2011-12-02 12:59 ` Dave Martin
2011-12-02 12:59 ` Dave Martin
2011-12-02 13:25 ` Nicolas Ferre
2011-12-02 13:25 ` Nicolas Ferre
2011-12-02 13:51 ` Rob Herring
2011-12-02 13:51 ` Rob Herring
2011-12-02 14:30 ` Dave Martin
2011-12-02 14:30 ` Dave Martin
2011-12-02 13:30 ` [PATCH v2] " Nicolas Ferre
2011-12-02 13:30 ` Nicolas Ferre
2011-12-02 13:30 ` Nicolas Ferre
2011-12-02 13:44 ` Dave Martin
2011-12-02 13:44 ` Dave Martin
2011-12-02 13:44 ` Dave Martin
2011-12-08 9:37 ` Nicolas Ferre
2011-12-08 9:37 ` Nicolas Ferre
2011-12-08 9:37 ` Nicolas Ferre
2011-12-08 13:30 ` Rob Herring [this message]
2011-12-08 13:30 ` Rob Herring
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=4EE0BBE3.60508@gmail.com \
--to=robherring2@gmail.com \
--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.