mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jon Loeliger <jdl@jdl.com>,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] Globally s/struct irq_host/struct irq_domain/
Date: Tue, 5 Oct 2010 09:25:44 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1010050925260.2556@localhost6.localdomain6> (raw)
In-Reply-To: <AANLkTimGtuq8+yA121xg0tVQ=Z=nqfzUG6BC8YqzX3Qh@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1705 bytes --]

On Mon, 4 Oct 2010, Grant Likely wrote:

> On Mon, Oct 4, 2010 at 5:09 PM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > On Mon, 2010-10-04 at 10:52 -0600, Grant Likely wrote:
> >> On Sun, Oct 03, 2010 at 02:03:57PM -0500, Jon Loeliger wrote:
> >> >
> >> > Just rename the irq_host structure as irq_domain to lessen the
> >> > confusion around the word "host".  Updated a few comments and
> >> > error messages to use "irq_domain" when refering to the structure.
> >> >
> >> > Suggested by Ben Herrenschmidt on the device-tree mailing list.
> >> >
> >> > Signed-off-by: Jon Loeliger <jdl@jdl.com>
> >> > ---
> >> >
> >> > Grant requested one giant patch simply renaming the structure.
> >>
> >> Thanks Jon,
> >>
> >> However, considering that tglx has already embarked on his Grand IRQ
> >> Subsystem Cleanup, I suspect that this will end up just getting in the
> >> way unless he picks it up into his queue.  It may even by that the
> >> need for irq_host will disappear once Thomas is finished by merging it
> >> into the core code.  I'd like to sit tight on this until the details
> >> of what powerpc virqs can be worked out with Ben and Thomas.
> >
> > I doubt the need for irq_host will disappear. However I don't see that
> > going into the core under that name, so I think the rename is a very
> > valid thing to do now. We just need to sync the patches to avoid pure
> > mechanical clash.
> >
> > Thomas initial series doesn't yet generalize the virq layer and that
> > will take a bit longer, so I'm happy to see Jon stuff go upstream first.
> 
> Alright, should tglx pick up this patch, or do you want to carry it in
> the powerpc tree?

Should go through powerpc.

       tglx

      reply	other threads:[~2010-10-05  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

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=alpine.LFD.2.00.1010050925260.2556@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jdl@jdl.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®