linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Stoica <cristian.stoica@freescale.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
	<horia.geanta@freescale.com>, <tudor.ambarus@freescale.com>
Subject: Re: [PATCH] crypto: testmgr: notify expected failures on aead tests
Date: Tue, 20 Jan 2015 09:58:58 +0200	[thread overview]
Message-ID: <54BE0AC2.4020607@freescale.com> (raw)
In-Reply-To: <20150120033549.GA10814@gondor.apana.org.au>

On 01/20/2015 05:35 AM, Herbert Xu wrote:
> No, I'm not going to create spam in everybody's dmesg just so that
> you can make sense of the spam coming from one driver.

Indeed, I found that it makes things far worse for the rest of the
drivers and the clarity improvement is questionable.
It was a bad idea.

Cristian S.

      reply	other threads:[~2015-01-20  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 13:54 [PATCH] crypto: testmgr: notify expected failures on aead tests Cristian Stoica
2015-01-20  3:35 ` Herbert Xu
2015-01-20  7:58   ` 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=54BE0AC2.4020607@freescale.com \
    --to=cristian.stoica@freescale.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@freescale.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tudor.ambarus@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).