From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Mohammed, Afzal" <afzal@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH] ARM: OMAP2+: irq: Increase no of supported interrupts to 128
Date: Thu, 10 May 2012 15:10:13 -0700 [thread overview]
Message-ID: <20120510221012.GP21851@atomide.com> (raw)
In-Reply-To: <87d36bvh9a.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120510 14:53]:
> "Hiremath, Vaibhav" <hvaibhav@ti.com> writes:
> >
> > Let me finish up with am33xx baseport upstream activity which is currently
> > going on at full swing, then next thing I will pick up is this code cleanup.
> >
> > I still feel, this is still a valid cleanup patch, and can be merged, as it
> > is required/used when we do major cleanup.
>
> Well, Tony can make that decision.
>
> Personally, I think this patch continues to add confusion on top of an
> existing mess, and to me provides the proverbial straw that broke the
> camel's back.
>
> That being said, the INTC core is an obviously important and sensitive
> piece of code so needs to be handled with care.
>
> In case Tony decides to merge this patch and allow a future** cleanup,
> I'll provide some comments.
Heh I agree with Kevin here :)
Tony
> ** since they rarely happen, we tend to not have too much faith in
> promises of mythical "future" cleanups. This is not because we don't
> trust you personally, but simply based on based experience.
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: irq: Increase no of supported interrupts to 128
Date: Thu, 10 May 2012 15:10:13 -0700 [thread overview]
Message-ID: <20120510221012.GP21851@atomide.com> (raw)
In-Reply-To: <87d36bvh9a.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120510 14:53]:
> "Hiremath, Vaibhav" <hvaibhav@ti.com> writes:
> >
> > Let me finish up with am33xx baseport upstream activity which is currently
> > going on at full swing, then next thing I will pick up is this code cleanup.
> >
> > I still feel, this is still a valid cleanup patch, and can be merged, as it
> > is required/used when we do major cleanup.
>
> Well, Tony can make that decision.
>
> Personally, I think this patch continues to add confusion on top of an
> existing mess, and to me provides the proverbial straw that broke the
> camel's back.
>
> That being said, the INTC core is an obviously important and sensitive
> piece of code so needs to be handled with care.
>
> In case Tony decides to merge this patch and allow a future** cleanup,
> I'll provide some comments.
Heh I agree with Kevin here :)
Tony
> ** since they rarely happen, we tend to not have too much faith in
> promises of mythical "future" cleanups. This is not because we don't
> trust you personally, but simply based on based experience.
next prev parent reply other threads:[~2012-05-10 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 14:17 [PATCH] ARM: OMAP2+: irq: Increase no of supported interrupts to 128 Vaibhav Hiremath
2012-05-08 14:17 ` Vaibhav Hiremath
2012-05-08 18:39 ` Kevin Hilman
2012-05-08 18:39 ` Kevin Hilman
2012-05-09 9:58 ` Hiremath, Vaibhav
2012-05-09 9:58 ` Hiremath, Vaibhav
2012-05-10 21:49 ` Kevin Hilman
2012-05-10 21:49 ` Kevin Hilman
2012-05-10 22:10 ` Tony Lindgren [this message]
2012-05-10 22:10 ` Tony Lindgren
2012-05-11 6:56 ` Hiremath, Vaibhav
2012-05-11 6:56 ` Hiremath, Vaibhav
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=20120510221012.GP21851@atomide.com \
--to=tony@atomide.com \
--cc=afzal@ti.com \
--cc=hvaibhav@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.