linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabor Juhos <juhosg@openwrt.org>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: mcgrof@infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] initvals: use SHA1 for verifying initval arrays
Date: Wed, 21 Dec 2011 19:10:31 +0100	[thread overview]
Message-ID: <4EF22117.7070803@openwrt.org> (raw)
In-Reply-To: <CAB=NE6WS6wasEEqFJ7RB7CMKYi=_RTjYJFRYLJc-_qq_-zJSuw@mail.gmail.com>

2011.12.21. 18:02 keltezéssel, Luis R. Rodriguez írta:
> In the future you may want to do this for patches with a patch in the
> commit log:
> 
> $ cat csumtest.patch | awk '{print "\t"$0}'
> 
> As otherwise git will treat this as part of your patch.

Ok, I will do that next time.

> This is *really* *really* sexy, thanks, applied and pushed!

Thanks!

-Gabor

      reply	other threads:[~2011-12-21 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 12:23 [PATCH] initvals: use SHA1 for verifying initval arrays Gabor Juhos
2011-12-21 17:02 ` Luis R. Rodriguez
2011-12-21 18:10   ` Gabor Juhos [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=4EF22117.7070803@openwrt.org \
    --to=juhosg@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@infradead.org \
    --cc=rodrigue@qca.qualcomm.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).