From: Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
To: Brian Niebuhr <BNiebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
Subject: Re: [PATCH 1/2 v2] spi: overhaul davinci spi driver to correct multiple errors
Date: Mon, 15 Mar 2010 08:50:13 -0700 [thread overview]
Message-ID: <87r5nl1t56.fsf@deeprootsystems.com> (raw)
In-Reply-To: <A117B9F753B6EB4580D381ED91D0FED00178A905-o2xmcm0DlSXTuRhSVNLHwoz1bQe5IM3EhPhL2mjWHbk@public.gmane.org> (Brian Niebuhr's message of "Mon\, 15 Mar 2010 09\:24\:35 -0500")
Brian Niebuhr <BNiebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org> writes:
> > > This patch is a significant overhaul of the davinci spi
>> controller driver
>> > that corrects multiple errors:
>> >
>> > - Eliminate a race condition that exists for slow SPI devices
>> > - Fix DMA transfer length error
>> > - Fix limitations preventing multiple SPI devices on the
>> same controller
>> >
>> > Signed-off-by: Brian Niebuhr <bniebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org>
>>
>> The verbose description of the issues addressed from PATCH 0/2 should
>> go here is well so it makes it into the permanent git history.
>
> I can certainly do that.
>
>> That being said, I think for the sake of reviewing, you're going to
>> need to break this up into reviewable pieces, each having a verbose
>> description of the issues being solved.
>>
>> There is also a mixture of fixes, enhancements, renames etc. These
>> should be done as separate patches.
>>
>> I know that it's more work to break it up like this, but that's the
>> only way to make a large change like this reviewable by others.
>
> I guess I was hoping that this could be reviewed as if it were a new
> driver submission. I ended up more or less rewriting all of the
> functional parts of the driver (txrx_bufs(), chipselect(), IRQs and DMA
> callbacks), so it's very difficult to show this as a series of changes.
> I do understand the problem from your perspective, though. My thought
> was that if the TI folks were willing to look the driver over and they
> gave their blessing, that you would look at it as if it were a
> replacement driver and accept or deny it on that basis.
I'm OK with the approach of considering it as a brand new driver. The
changelog made me think it was a bunch of fixes/enhancements and not a
re-write.
It should then be made more clear in the changelog that this is
essentially a re-write, and why it is not done in a series of small
changes.
Whichever approach, this will need to worked out between you and the
origial TI authors (Sandeep, Sudahkar) who will need to review/signoff
this replacement.
Kevin
next prev parent reply other threads:[~2010-03-15 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 19:35 [PATCH 0/2 v2] overhaul davinci spi driver to fix multiple errors Brian Niebuhr
[not found] ` <1268422520-22642-1-git-send-email-bniebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org>
2010-03-12 19:35 ` [PATCH 1/2 v2] spi: overhaul davinci spi driver to correct " Brian Niebuhr
[not found] ` <1268422520-22642-2-git-send-email-bniebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org>
2010-03-12 19:35 ` [PATCH 2/2 v2] spi: modify davinci platform data for updated driver Brian Niebuhr
2010-03-13 0:22 ` [PATCH 1/2 v2] spi: overhaul davinci spi driver to correct multiple errors Kevin Hilman
[not found] ` <87k4th2hpn.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-03-15 14:24 ` Brian Niebuhr
[not found] ` <A117B9F753B6EB4580D381ED91D0FED00178A905-o2xmcm0DlSXTuRhSVNLHwoz1bQe5IM3EhPhL2mjWHbk@public.gmane.org>
2010-03-15 15:50 ` Kevin Hilman [this message]
[not found] ` <87r5nl1t56.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-03-17 14:32 ` Sudhakar Rajashekhara
2010-03-17 14:32 ` Sudhakar Rajashekhara
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=87r5nl1t56.fsf@deeprootsystems.com \
--to=khilman-1d3hcaltpluheniveurvkkeocmrvltnr@public.gmane.org \
--cc=BNiebuhr-JaPwekKOx1yaMJb+Lgu22Q@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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.