mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: jesper.juhl@gmail.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	herbert@gondor.apana.org.au, sri@us.ibm.com,
	bfields@fieldses.org, yoshfuji@linux-ipv6.org,
	breed@users.sourceforge.net, andros@citi.umich.edu,
	adobriyan@mail.ru
Subject: Re: [PATCH] crypto_free_tfm callers no longer need to check for NULL
Date: Thu, 01 Sep 2005 15:31:42 -0700 (PDT)	[thread overview]
Message-ID: <20050901.153142.18055974.davem@davemloft.net> (raw)
In-Reply-To: <200508312220.14929.jesper.juhl@gmail.com>


Applied, thanks Jesper.

Can you avoid those "/./" things from showing up in the file paths of
the patches you post?  They upset the GIT patch application scripts
and diff verifiers, so I had to edit them out by hand.

Thanks again.

       reply	other threads:[~2005-09-01 22:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200508312220.14929.jesper.juhl@gmail.com>
2005-09-01 22:31 ` David S. Miller [this message]
2005-09-01 22:45   ` Jesper Juhl

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=20050901.153142.18055974.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adobriyan@mail.ru \
    --cc=akpm@osdl.org \
    --cc=andros@citi.umich.edu \
    --cc=bfields@fieldses.org \
    --cc=breed@users.sourceforge.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sri@us.ibm.com \
    --cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®