From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] Globally s/struct irq_host/struct irq_domain/
Date: Fri, 21 Jan 2011 12:02:28 -0600 [thread overview]
Message-ID: <E1PgLJc-0005rB-CP@jdl.com> (raw)
In-Reply-To: <AANLkTi=bHV9XJoUT_ki1Eziq5fM3DekrOLoFuNzGGv91-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
>
> I always reserve the right to change my mind. }:->
Naturally!
> Sorry about that,
No problem. The thought back then was that we'd hit the "global"
piece and then we'd buy the time to hit the local pieces as we could.
> but I actually applied the patch this morning with the thought that
> I'd get Linus to pick it up late to avoid collisions in linux-next.
Makes sense.
> However, when I actually looked at the result I realized that at the
> very least, the irq_host_ops, the #defines, and the irq_*_host
> functions absolutely have to be renamed at the same time. Not
> necessarily in the same patch, but definitely at the same time.
Will do!
jdl
next prev parent reply other threads:[~2011-01-21 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 13:53 [PATCH] Globally s/struct irq_host/struct irq_domain/ Jon Loeliger
[not found] ` <E1Pd18R-0002d3-US-CYoMK+44s/E@public.gmane.org>
2011-01-12 15:58 ` Josh Boyer
2011-01-21 17:13 ` Grant Likely
[not found] ` <20110121171314.GD7477-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-01-21 17:19 ` Jon Loeliger
2011-01-21 17:28 ` Grant Likely
[not found] ` <AANLkTi=bHV9XJoUT_ki1Eziq5fM3DekrOLoFuNzGGv91-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-21 18:02 ` Jon Loeliger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-03 19:03 Jon Loeliger
2010-10-04 16:52 ` Grant Likely
2010-10-04 23:09 ` Benjamin Herrenschmidt
2010-10-05 0:36 ` Jon Loeliger
2010-10-05 3:00 ` Grant Likely
2010-10-05 7:25 ` Thomas Gleixner
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=E1PgLJc-0005rB-CP@jdl.com \
--to=jdl-cyomk+44s/e@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).