public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] (xen) stable/pci.cleanups.v1 for 3.1
Date: Thu, 21 Jul 2011 23:33:21 -0400	[thread overview]
Message-ID: <20110722033321.GB22901@dumpdata.com> (raw)

Hey Linus,

Please pull the following branch:

git pull git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/pci.cleanups.v1

which has patches since git commit 075d9db13183c102770dc6cefabfee1b832f9614
Linus Torvalds (1):
    Merge branch 'stable/bug.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen

This patchset cleans ups the Xen PCI glue code. No major improvements but it sure
makes the code easier to read.

Konrad Rzeszutek Wilk (10):
      xen/pci: Shuffle code around.
      xen/pci: Update comments and fix empty spaces.
      xen/pci: Provide #ifdef CONFIG_ACPI to easy code squashing.
      xen/pci: In xen_register_pirq bind the GSI to the IRQ after the hypercall.
      xen/pci: Use the xen_register_pirq for HVM and initial domain users
      xen/pci: Squash pci_xen_initial_domain and xen_setup_pirqs together.
      xen/pci: Move the allocation of IRQs when there are no IOAPIC's to the end
      xen/pci: Retire unnecessary #ifdef CONFIG_ACPI
      xen/pci: Remove 'xen_allocate_pirq_gsi'.
      xen/pci: Use 'acpi_gsi_to_irq' value unconditionally.

 arch/x86/include/asm/xen/pci.h |    5 +-
 arch/x86/pci/xen.c             |  371 +++++++++++++++++-----------------------
 drivers/xen/events.c           |    7 +-
 include/xen/events.h           |    2 -
 4 files changed, 165 insertions(+), 220 deletions(-)

                 reply	other threads:[~2011-07-22  3:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110722033321.GB22901@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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