From: David Daney <ddaney.cavm@gmail.com>
To: ralf@linux-mips.org, linux-ide@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>
Subject: [PATCH 0/2] ata: Updates for pata_octeon_cf driver.
Date: Fri, 17 Aug 2012 16:54:31 -0700 [thread overview]
Message-ID: <1345247673-25086-1-git-send-email-ddaney.cavm@gmail.com> (raw)
From: David Daney <david.daney@cavium.com>
The main update is conversion to device tree. Now the the OCTEON
device tree prerequisites are upstream, we can convert the
pata_octeon_cf driver.
The second change allows the driver to function when the kernel is
built for little-endian operation.
The only real change in the MIPS portion of the tree is deletion of
crap.
There is a dependence on patches Ralf has queued in linux-next so it
may be best to merge via the MIPS tree (as pata_octeon_cf only exists
in MIPS based OCTEON SOCs). But the ata tree would be fine by me too.
In any even we may need some cross sub-system Acked-bys.
David Daney (2):
MIPS/OCTEON/ata: Convert pata_octeon_cf.c to use device tree.
ata: pata_octeon_cf: Use correct byte order for DMA in when built
little-endian.
arch/mips/cavium-octeon/octeon-irq.c | 1 -
arch/mips/cavium-octeon/octeon-platform.c | 102 ------
arch/mips/include/asm/mach-cavium-octeon/irq.h | 1 -
arch/mips/include/asm/octeon/octeon.h | 7 -
drivers/ata/pata_octeon_cf.c | 423 +++++++++++++++++--------
5 files changed, 288 insertions(+), 246 deletions(-)
--
1.7.11.2
next reply other threads:[~2012-08-17 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 23:54 David Daney [this message]
2012-08-17 23:54 ` [PATCH 1/2] MIPS/OCTEON/ata: Convert pata_octeon_cf.c to use device tree David Daney
2012-08-17 23:54 ` [PATCH 2/2] ata: pata_octeon_cf: Use correct byte order for DMA in when built little-endian David Daney
2012-08-18 0:19 ` [PATCH 0/2] ata: Updates for pata_octeon_cf driver Jeff Garzik
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=1345247673-25086-1-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=david.daney@cavium.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).