From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: spi-devel-general@lists.sourceforge.net,
"Bryan Wu" <bryan.wu@analog.com>,
linux-kernel@vger.kernel.org
Subject: Re: [spi-devel-general] [PATCH 0/6] [Blackfin] SPI driver updates
Date: Fri, 1 Feb 2008 17:41:14 +0800 [thread overview]
Message-ID: <386072610802010141g340cdb14gcd244ab87ffc855e@mail.gmail.com> (raw)
In-Reply-To: <200801311250.46415.david-b@pacbell.net>
On Feb 1, 2008 4:50 AM, David Brownell <david-b@pacbell.net> wrote:
> I've forwarded these to Andrew, with my signoff and updated comments.
> You still need to work on having your patch descriptions match up
> to what the patches actually do...
>
Thanks a lot, I will try to make it more clearer next time.
> Patches 3-5 in this series seem to have a common thread: waiting
> until BIT_STAT_SPIF is set before moving to the next step of the
> transfer. Next time something similar happens, I'd rather see just
> one patch addressing the issue on all code paths ... not three small
> patches that only fix it for a few of the code paths.
>
OK, I will try to merge these same bug fixing into one patch.
> Also, two of those three patches describe their updates as fixing
> a "regression", or "reverting" the code. Was this a bug that came
> in those patches you wanted to merge to 2.6.24? If so, shouldn't
> those regression fixes go into the stable series?
>
Yes, I agree with you. Actually, I intend to send out these bug fixing
patch ASAP, but we want to make sure our tester verify this bug was
fixing first.
Thanks
-Bryan
prev parent reply other threads:[~2008-02-01 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 9:13 Bryan Wu
2008-01-30 9:13 ` [PATCH 1/6] [Blackfin] SPI driver: remove useless return status check in restore_state function pointed by Michael Bryan Wu
2008-01-30 9:13 ` [PATCH 2/6] [Blackfin] SPI driver: Use SPI device name to do gpio peripheral request Bryan Wu
2008-01-30 21:48 ` [spi-devel-general] " David Brownell
2008-01-31 3:12 ` Bryan Wu
2008-01-30 9:13 ` [PATCH 3/6] [Blackfin] SPI driver: fix bug - PBX cannot work with this SPI framework driver Bryan Wu
2008-01-30 9:13 ` [PATCH 4/6] [Blackfin] SPI driver: fix bug - SPI duplex operation can read a dummy byte at the first transfer Bryan Wu
2008-01-30 9:13 ` [PATCH 5/6] [Blackfin] SPI driver: Fix bug SPI_write should not return until complete bit is set Bryan Wu
2008-01-30 9:13 ` [PATCH 6/6] [Blackfin] SPI driver: use simpler comment headers and strip out information that is maintained in the scm's log Bryan Wu
2008-01-31 20:50 ` [spi-devel-general] [PATCH 0/6] [Blackfin] SPI driver updates David Brownell
2008-02-01 9:41 ` Bryan Wu [this message]
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=386072610802010141g340cdb14gcd244ab87ffc855e@mail.gmail.com \
--to=cooloney.lkml@gmail.com \
--cc=bryan.wu@analog.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®