linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Stoica <cristian.stoica@freescale.com>
To: "Horia Geantă" <horia.geanta@freescale.com>,
	linux-crypto@vger.kernel.org
Cc: <herbert@gondor.apana.org.au>, <linux-kernel@vger.kernel.org>,
	<davem@davemloft.net>
Subject: Re: [PATCH 2/3] crypto: testmgr.c: white space removal on __test_skcipher
Date: Mon, 11 Aug 2014 09:33:50 +0300	[thread overview]
Message-ID: <53E863CE.3060509@freescale.com> (raw)
In-Reply-To: <53E733EF.80003@freescale.com>

Hi Horia,

On 10.08.2014 11:57, Horia Geantă wrote:
> On 8/8/2014 2:27 PM, Cristian Stoica wrote:
> Don't add more checkpatch warnings on top of existing ones.

I've weighted all the checkpatch warnings and errors introduced by these
patches and I've found them fair versus Linux coding style guide.

If these are the only barriers to acceptance then I'll consider an
update if Herbert agrees with the patches:

> WARNING: line over 80 characters
> #58: FILE: crypto/testmgr.c:992:
> 
>> +			crypto_ablkcipher_set_flags(tfm, CRYPTO_TFM_REQ_WEAK_KEY);

This line is 82 chars long. I find it slightly more readable than the
alternative[s].

"The limit on the length of lines is 80 columns and this is a strongly
preferred limit [...] unless exceeding 80 columns significantly
increases readability and does not hide information"

Now this is a debate about "slightly" vs "significantly". Have fun.

Cristian S.

  reply	other threads:[~2014-08-11  6:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 10:11 [PATCH] crypto: testmgr.c: white space fix-ups on test_aead Cristian Stoica
2014-08-08  9:22 ` Horia Geantă
2014-08-08 11:27   ` [PATCH 1/3] crypto: testmgr.c: white space removal on __test_hash Cristian Stoica
2014-08-08 11:27     ` [PATCH 2/3] crypto: testmgr.c: white space removal on __test_skcipher Cristian Stoica
2014-08-10  8:57       ` Horia Geantă
2014-08-11  6:33         ` Cristian Stoica [this message]
2014-08-08 11:27     ` [PATCH 3/3] crypto: testmgr.c: delay execution of set-up code Cristian Stoica
2014-08-25 12:40 ` [PATCH] crypto: testmgr.c: white space fix-ups on test_aead Herbert Xu

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=53E863CE.3060509@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=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).