From: Ned Forrester <nforrester-/d+BM93fTQY@public.gmane.org>
To: Eric Miao <ymiao3-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Cc: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.org
Subject: Re: 2006/1/28 patches to pxa2xx-spi in 2.6.25 tree
Date: Thu, 14 Feb 2008 20:09:55 -0500 [thread overview]
Message-ID: <47B4E663.7050001@whoi.edu> (raw)
In-Reply-To: <E913911567467945BBEB9277E27868B0880975-3TKN+kxLw8+HXkj8w7BxOhL4W9x8LtSr@public.gmane.org>
Eric Miao wrote:
> Let me clarify:
>
> Yes, I apologize I break the potential rules here for two reasons:
>
> 1. I was not aware of the existence of spi-devel-general mailinglist
> at that time (I know this now :)
>
> 2. This patch is one of the series of patches refactoring PXA/ARM SSP
> code, and the other patches are tightly PXA/ARM related, and David
> reviewed part of the patch if not all.
I guess change is the price of progress.
> And indeed yes, I will fire another patch correcting the doc, maybe
> after another round of SSP code clean-up.
Thanks.
> Any other concerns/issues about the driver, please make me CC'ed, so
> I'll try fix them if Stephen isn't available.
The only outstanding issue that I am aware of is a minor problem with
the sequence of setting chip select that was discussed on
spi-devel-general this week. Stephen has not chimed in on that issue,
so I will submit a patch for that myself, either tomorrow or early next
week. I will do this patch so that it won't break a heavily modified
version of pxa2xx_spi.c that I am working on, which deals with chained
transfers using DMA descriptors (don't expect to ever see it submitted
for inclusion in the kernel, but I am trying to stay in sync, anyway).
I have examined the patches you submitted, so far, and I think they do
not interfere with my version. Someday I will be able to test, but I
work from the distribution provided with the Gumstix computers, and they
are currently at 2.6.21 (and I am still at 2.6.20), so it may be a year
or more before I see 2.6.25.
--
Ned Forrester nforrester-/d+BM93fTQY@public.gmane.org
Oceanographic Systems Lab 508-289-2226
Applied Ocean Physics and Engineering Dept.
Woods Hole Oceanographic Institution Woods Hole, MA 02543, USA
http://www.whoi.edu/sbl/liteSite.do?litesiteid=7212
http://www.whoi.edu/hpb/Site.do?id=1532
http://www.whoi.edu/page.do?pid=10079
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-15 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 21:45 2006/1/28 patches to pxa2xx-spi in 2.6.25 tree Ned Forrester
2008-02-15 0:42 ` Eric Miao
[not found] ` <E913911567467945BBEB9277E27868B0880975-3TKN+kxLw8+HXkj8w7BxOhL4W9x8LtSr@public.gmane.org>
2008-02-15 1:09 ` Ned Forrester [this message]
2008-02-23 2:44 ` David Brownell
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=47B4E663.7050001@whoi.edu \
--to=nforrester-/d+bm93ftqy@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.org \
--cc=ymiao3-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.