From: Cristian Stoica <cristian.stoica@freescale.com>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<horia.geanta@freescale.com>, <marex@denx.de>
Subject: Re: [PATCH] crypto: caam: fix error reporting
Date: Wed, 5 Nov 2014 11:27:37 +0200 [thread overview]
Message-ID: <5459ED89.2080109@freescale.com> (raw)
In-Reply-To: <20141104105731.ccb0eedea154b9bb6ed195b3@freescale.com>
Hi Kim,
On 11/04/2014 06:57 PM, Kim Phillips wrote:
> On Tue, 4 Nov 2014 10:57:57 +0200
> Cristian Stoica <cristian.stoica@freescale.com> wrote:
>> Do you want me to drop the patch and pretend there is nothing to see?
>
> no, fixing potential bugs preemptively is fine; I'd just like to
> know that's the case: it wasn't clear from the original commit
> message whether the problem occurred on a new h/w revision, in which
> case I'd have like to have seen the driver updated with support for
> the new error codes.
This is a preemptive fix. I did not see a problem in the field with any
hardware, recent or old.
Cristian S.
prev parent reply other threads:[~2014-11-05 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:57 [PATCH] crypto: caam: fix error reporting Cristian Stoica
2014-10-31 18:22 ` Kim Phillips
2014-11-01 11:43 ` Marek Vasut
2014-11-03 9:18 ` Cristian Stoica
2014-11-03 19:47 ` Kim Phillips
2014-11-04 8:57 ` Cristian Stoica
2014-11-04 16:57 ` Kim Phillips
2014-11-05 9:21 ` [PATCH v2] " Cristian Stoica
2014-11-05 16:43 ` Kim Phillips
2014-11-06 8:01 ` Cristian Stoica
2014-11-06 15:17 ` Herbert Xu
2014-11-05 9:27 ` Cristian Stoica [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=5459ED89.2080109@freescale.com \
--to=cristian.stoica@freescale.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@freescale.com \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
/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.