From: Jiang Liu <jiang.liu@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Yijing Wang <wangyijing@huawei.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Ingo Molnar <mingo@kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: Hierarchical irqdomains - Status update
Date: Mon, 24 Nov 2014 15:20:57 +0800 [thread overview]
Message-ID: <5472DC59.5040407@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1411231915010.6439@nanos>
On 2014/11/24 3:03, Thomas Gleixner wrote:
> Folks,
>
> I've rebased the hierarchical irqdomain code on top of Bjorns
> msi_controller rework.
>
> Changes versus the previous version:
>
> - Bjorns new pci/mci branch. See also:
> http://lkml.kernel.org/r/20141121172018.GA6578@google.com
>
> Thanks Bjorn for fixing that just before your vacation!
>
> - Rename of msi_mask/unmask_irq et al so it's clear that these
> functions are PCI related and cannot be used for non PCI based
> MSI functionality.
>
> - Folded back fixup patches
>
> - Added the missing parent check as reported by Suravee
>
> The branch is now immutable and you can base your patches on it.
>
> If you need to pull the branch into your tree, please let me know.
>
> Patches which are mostly touching drivers/irqchip should go through
> Jason. Please post them against irq/irqdomain. We'll either create a
> seperate branch for them or merge irq/irqdomain into irq/core.
>
> Thanks for the fruitful discussions, testing, rebasing and patience.
Thanks for your great support to enable hierarchy irqdomain.
Learned much about how to organize patches:)
>
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2014-11-24 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 19:03 Thomas Gleixner
2014-11-24 7:20 ` Jiang Liu [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=5472DC59.5040407@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=bhelgaas@google.com \
--cc=grant.likely@linaro.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=wangyijing@huawei.com \
--cc=yingjoe.chen@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome