From: Grant Likely <grant.likely@secretlab.ca>
To: "Richard Röjfors" <richard.rojfors@mocean-labs.com>
Cc: spi-devel-general@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
dbrownell@users.sourceforge.net, John Linn <John.Linn@xilinx.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v3 0/4] xilinx_spi: Split into platform and of driver, support new IP, platform independence.
Date: Fri, 13 Nov 2009 11:29:46 -0700 [thread overview]
Message-ID: <fa686aa40911131029uddb497ah7907ccd9dc23c6e3@mail.gmail.com> (raw)
In-Reply-To: <4AFD50F0.6050805@mocean-labs.com>
On Fri, Nov 13, 2009 at 5:28 AM, Richard Röjfors
<richard.rojfors@mocean-labs.com> wrote:
> Hi,
>
> To follow is a series of patches against the xilinx_spi driver.
>
> The patchset is against 2.6.32-rc6
>
> The patchset addresses several problems in the current driver:
> * It's PPC only (OF and uses PPC specific memory operations)
> * Only supporting big endian writes
> * Supports only 8bit SPI, support for DS570 (also 16 or 32 bit) is added.
> * A platform driver is introduced for non OF capable architectures.
>
> These patches were posted as one big patch up to 4 iterations, not splitted into 4.
>
> This version, 3, is updated after review from Grant Likely and John Linn
>
> John Linn has also tested the code on PPC, I have only tested on X86.
Applied to my 'test' branch on git.secretlab.ca. There was a conflict
on patch 3/4 with a previous bugfix from John Linn. Please check that
I've fixed it up correctly.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-11-13 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 12:28 [PATCH v3 0/4] xilinx_spi: Split into platform and of driver, support new IP, platform independence Richard Röjfors
2009-11-13 18:29 ` Grant Likely [this message]
2009-11-13 19:59 ` John Linn
2009-11-13 20:13 ` Grant Likely
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=fa686aa40911131029uddb497ah7907ccd9dc23c6e3@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=John.Linn@xilinx.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=richard.rojfors@mocean-labs.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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).