From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>,
Ingo Molnar <mingo@elte.hu>,
Giancarlo Asnaghi <giancarlo.asnaghi@st.com>,
Alan Cox <alan@linux.intel.com>
Subject: [PATCH V3 0/3] STA2X11: patches for pci bridge support
Date: Wed, 22 Feb 2012 23:13:57 +0100 [thread overview]
Message-ID: <cover.1329947637.git.rubini@gnudd.com> (raw)
This series is V3 of what I sent on Jan 30th as V2.
Patch 3 is dependent on patch 1 and 2, which are unordered. When I
posted V2 of this set, patch 3 was picked up, but compilation failed
because of the missing prerequisites. Also, some prototypes changed
in the meanwhile and patch 3 was miscompiling in linux-next so it
has been correctly dropped.
V3: rebased on next-20120221. Fixed patch 3 to match new DMA
prototypes. Renamed patch 3 as Ingo and Jesse merged it. Added both of
them to explicit Cc: list in the email set.
V2: rebased, minor and less-minor changes in patch 3/3.
Alessandro Rubini (3):
x86: introduce CONFIG_X86_DEV_DMA_OPS
x86: introduce CONFIG_X86_DMA_REMAP
x86/PCI: initial support for sta2x11 I/O hub
arch/x86/Kconfig | 34 +++-
arch/x86/include/asm/device.h | 4 +-
arch/x86/include/asm/dma-mapping.h | 9 +-
arch/x86/pci/Makefile | 2 +
arch/x86/pci/sta2x11-fixup.c | 367 ++++++++++++++++++++++++++++++++++++
5 files changed, 409 insertions(+), 7 deletions(-)
create mode 100644 arch/x86/pci/sta2x11-fixup.c
--
1.7.7.2
next reply other threads:[~2012-02-22 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 22:13 Alessandro Rubini [this message]
2012-02-22 22:14 ` [PATCH V3 1/3] x86: introduce CONFIG_X86_DEV_DMA_OPS Alessandro Rubini
2012-02-22 22:14 ` [PATCH V3 2/3] x86: introduce CONFIG_X86_DMA_REMAP Alessandro Rubini
2012-02-22 22:14 ` [PATCH V3 3/3] x86/PCI: initial support for sta2x11 I/O hub Alessandro Rubini
2012-02-23 16:28 ` [PATCH V3 0/3] STA2X11: patches for pci bridge support Jesse Barnes
2012-03-01 22:30 ` Alessandro Rubini
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=cover.1329947637.git.rubini@gnudd.com \
--to=rubini@gnudd.com \
--cc=alan@linux.intel.com \
--cc=giancarlo.asnaghi@st.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome