From: Thomas Gleixner <tglx@linutronix.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [patch 0/4] XEN: Interrupt cleanups
Date: Mon, 7 Feb 2011 22:33:50 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1102072231220.31804@localhost6.localdomain6> (raw)
In-Reply-To: <4D50641B.2090006@goop.org>
Jeremy,
On Mon, 7 Feb 2011, Jeremy Fitzhardinge wrote:
> On 02/05/2011 12:08 PM, Thomas Gleixner wrote:
> > the following series converts the interrupt chips of XEN to the new
> > chip functions and the last patches replace the xen private resume
> > hackery.
> >
> > The first two patches have no dependencies.
> >
> > The last two need the modification to the generic interrupt layer. I
> > could either carry them through the genirq tree with your
> > acked-tested-whatever-by or I provide you a branch to pull that change
> > from. I need the genirq change local as it conflicts with other patches
> > in the pipeline. Either way works fine.
>
> Hi Thomas,
>
> Thanks very much for looking at this. IanC also has some patches to
> clean up the Xen interrupt stuff to get rid of the local hacks, so I'll
> let him work out how to reconcile the two sets of work (ah, I see he's
> already replied).
>
> [Read patches]
>
> It doesn't look like there's any functional overlap at all, since his
> patches are concerned with using the core irq allocator rather than a
> private one, so that's OK.
>
> Anyway, I'll let Ian do the ack.
Ok. The irq_chip conversion is mostly mechanical, but I'm really
concerned about that IRQ_SUSPENDED hackery. It'd be nice if you
resp. Ian could give that a test ride. That would allow me to cleanup
stuff in the core code.
Thanks,
tglx
next prev parent reply other threads:[~2011-02-07 21:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 20:08 Thomas Gleixner
2011-02-05 20:08 ` [patch 1/4] xen: Remove stale irq_chip.end Thomas Gleixner
2011-02-05 20:08 ` [patch 2/4] xen: Switch to new irq_chip functions Thomas Gleixner
2011-02-07 11:08 ` Ian Campbell
2011-02-07 11:30 ` Thomas Gleixner
2011-02-05 20:08 ` [patch 3/4] genirq: Add IRQF_FORCE_RESUME Thomas Gleixner
2011-02-05 20:08 ` [patch 4/4] xen: Use IRQF_FORCE_RESUME Thomas Gleixner
2011-02-07 21:28 ` [patch 0/4] XEN: Interrupt cleanups Jeremy Fitzhardinge
2011-02-07 21:33 ` Thomas Gleixner [this message]
2011-02-07 21:57 ` Jeremy Fitzhardinge
2011-02-08 14:03 ` Ian Campbell
2011-02-08 14:55 ` Thomas Gleixner
2011-02-08 15:05 ` Ian Campbell
2011-02-08 15:39 ` Thomas Gleixner
2011-02-08 16:20 ` Konrad Rzeszutek Wilk
2011-02-08 16:31 ` Ian Campbell
2011-02-08 17:33 ` Thomas Gleixner
2011-02-08 18:39 ` Konrad Rzeszutek Wilk
2011-02-08 19:05 ` Thomas Gleixner
2011-02-09 9:27 ` Ian Campbell
2011-02-09 9:46 ` Thomas Gleixner
2011-02-09 9:48 ` Thomas Gleixner
2011-02-09 10:16 ` Ian Campbell
2011-02-09 9:56 ` Ian Campbell
2011-02-08 16:24 ` Konrad Rzeszutek Wilk
2011-02-08 17:38 ` Thomas Gleixner
2011-02-08 16:26 ` Ian Campbell
2011-02-07 21:56 ` Ian Campbell
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.1102072231220.31804@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.org \
--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®