From: Mark Brown <broonie@kernel.org>
To: Jonatas Rech <jonatas.rech@datacom.ind.br>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: fsl-espi: fix behaviour for full-duplex xfers
Date: Fri, 24 Apr 2015 19:17:45 +0100 [thread overview]
Message-ID: <20150424181745.GG22845@sirena.org.uk> (raw)
In-Reply-To: <20150423180622.GC12637@datacom.ind.br>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Thu, Apr 23, 2015 at 03:06:22PM -0300, Jonatas Rech wrote:
> I agree, but please note that this came up while I was trying to fix the
> full-duplex functionality, and it's a different problem. Fixing this would
> impact protocol drivers, as stated earlier. It would take some time for me to
> study other drivers and come up with the best solution for this driver plus
> (at least) the m25p80, which supports the hardware I currently have access to.
> I know this must be fixed, but wouldn't it be subject to a different patch?
> Thanks in advance for the advice.
The commit message says "this correction has exposed an inconsistency"
which suggests that the problem was masked before this fix. Did you
mean to say that while fixing this you noticed a separate bug that's
present anyway?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-24 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:23 [PATCH] spi: fsl-espi: fix behaviour for full-duplex xfers Jonatas Rech
2015-04-18 12:55 ` Mark Brown
2015-04-22 15:09 ` DATACOM - Jonatas.Rech
2015-04-22 19:57 ` Mark Brown
2015-04-23 18:06 ` Jonatas Rech
2015-04-24 18:17 ` Mark Brown [this message]
2015-04-24 20:03 ` Jonatas Rech
2015-04-25 13:01 ` Mark Brown
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=20150424181745.GG22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jonatas.rech@datacom.ind.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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