From: Alessandro Rubini <rubini@gnudd.com>
To: linux-kernel@vger.kernel.org
Cc: giancarlo.asnaghi@st.com, alan@linux.intel.com,
andrzej.p@samsung.com, mingo@elte.hu, jbarnes@virtuousgeek.org
Subject: [PATCH 0/3] STA2X11 fixes for next
Date: Thu, 16 Feb 2012 11:39:49 +0100 [thread overview]
Message-ID: <cover.1329387617.git.rubini@gnudd.com> (raw)
My patch to add sta2x11 initial support has been merged by Ingo Molnar
as commit 60dda96f, with signed-off by Jesse Barnes. However, it
depended on two config symbols (the patch was 3/3, actually) and
I'm to get the blame for not noting it when Jesse told me he would
merge the 3/3.
Additionally, commit aa04651 by Andrzej Pietrasiewicz changed some
prototypes we use, so stuff is not compiling any more if
CONFIG_STA2X11 is on.
I Cc: all involved parties in all patches. The commit
messages for the original patches have been reworded to match the fact
that they are going in after sta2x11-fixup.c . At this point, they
are all bugfix patches.
Alessandro Rubini (3):
x86/PCI: change sta2x11-fixup to account for commit aa04651
x86: introduce CONFIG_X86_DEV_DMA_OPS
x86: introduce CONFIG_X86_DMA_REMAP
arch/x86/Kconfig | 11 +++++++++++
arch/x86/include/asm/device.h | 4 ++--
arch/x86/include/asm/dma-mapping.h | 9 ++++++++-
arch/x86/pci/sta2x11-fixup.c | 12 +++++++-----
4 files changed, 28 insertions(+), 8 deletions(-)
--
1.7.7.2
next reply other threads:[~2012-02-16 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 10:39 Alessandro Rubini [this message]
2012-02-16 10:40 ` [PATCH 1/3] x86/PCI: change sta2x11-fixup to account for commit aa04651 Alessandro Rubini
2012-02-16 10:40 ` [PATCH 2/3] x86: introduce CONFIG_X86_DEV_DMA_OPS Alessandro Rubini
2012-02-16 10:40 ` [PATCH 3/3] x86: introduce CONFIG_X86_DMA_REMAP 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.1329387617.git.rubini@gnudd.com \
--to=rubini@gnudd.com \
--cc=alan@linux.intel.com \
--cc=andrzej.p@samsung.com \
--cc=giancarlo.asnaghi@st.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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