devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Sebastian Andrzej Siewior
	<bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Subject: Re: [PATCH] x86: convert to generic irq_domain
Date: Fri, 30 Dec 2011 09:22:40 -0600	[thread overview]
Message-ID: <4EFDD740.5080303@gmail.com> (raw)
In-Reply-To: <20111219144940.GI20801-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>

Sebastian,

On 12/19/2011 08:49 AM, Sebastian Andrzej Siewior wrote:
> * Rob Herring | 2011-12-16 23:18:49 [-0600]:
> 
>> This is needed to avoid struct collisions with the generic irq_domain
>> support being added to kernel/irq/generic-chip.c.
>>
>> Boot tested, but not on a DT enabled platform.
> 
> I had a patch in my tree for this and it did not work. One bug was fixed
> by eef24a ("irq: Fix check for already initialized irq_domain in
> irq_domain_add"). Something else come up after that. I will grab a board
> test it later and let you know :)
> 

Any update on testing this?

Rob

  parent reply	other threads:[~2011-12-30 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17  5:18 [PATCH] x86: convert to generic irq_domain Rob Herring
2011-12-19 14:49 ` Sebastian Andrzej Siewior
     [not found]   ` <20111219144940.GI20801-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2011-12-30 15:22     ` Rob Herring [this message]
2012-01-09  8:19       ` Sebastian Andrzej Siewior
     [not found] ` <1324099129-28832-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-15 16:35   ` Sebastian Andrzej Siewior
     [not found]     ` <20120115163538.GA19026-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2012-01-16 16:16       ` Grant Likely

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=4EFDD740.5080303@gmail.com \
    --to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@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).