Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: Richard Hartmann <richih.mailinglist@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] CRYPTO: Fix checkpatch errors & warnings in cipher.c
Date: Wed, 10 Feb 2010 03:21:26 +0100	[thread overview]
Message-ID: <2d460de71002091821h7b6e99b0gb8f134355f64c65a@mail.gmail.com> (raw)
In-Reply-To: <1265765446-24958-1-git-send-email-richih.mailinglist@gmail.com>

Obviously, this should have been named

CRYPTO: Fix checkpatch errors & warnings in compress.c

Should I re-send the patch or is it less noise & hassle if I just leave
it this way?


Richard

On Wed, Feb 10, 2010 at 02:30, Richard Hartmann
<richih.mailinglist@gmail.com> wrote:
>
> Signed-off-by: Richard Hartmann <richih.mailinglist@gmail.com>
> ---
>  crypto/compress.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/crypto/compress.c b/crypto/compress.c
> index 1ee3570..c33f076 100644
> --- a/crypto/compress.c
> +++ b/crypto/compress.c
> @@ -7,7 +7,7 @@
>  *
>  * This program is free software; you can redistribute it and/or modify it
>  * under the terms of the GNU General Public License as published by the Free
> - * Software Foundation; either version 2 of the License, or (at your option)
> + * Software Foundation; either version 2 of the License, or (at your option)
>  * any later version.
>  *
>  */
> @@ -39,7 +39,7 @@ int crypto_init_compress_ops(struct crypto_tfm *tfm)
>
>        ops->cot_compress = crypto_compress;
>        ops->cot_decompress = crypto_decompress;
> -
> +
>        return 0;
>  }
>
> --
> 1.6.6.1
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-02-10  2:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10  1:30 [PATCH 1/1] CRYPTO: Fix checkpatch errors & warnings in cipher.c Richard Hartmann
2010-02-10  2:21 ` Richard Hartmann [this message]
2010-02-11  4:46   ` Herbert Xu
2010-02-16 11:56     ` Richard Hartmann
2010-02-16 12:00       ` Herbert Xu
2010-02-16 12:06         ` Richard Hartmann
2010-02-16 12:21           ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2010-02-10  1:32 Richard Hartmann

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=2d460de71002091821h7b6e99b0gb8f134355f64c65a@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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