All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: "David S. Miller" <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Jouni Malinen <jkmaline@cc.hut.fi>,
	James Morris <jmorris@intercode.com.au>,
	Pedro Roque <roque@di.fc.ul.pt>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Kunihiro Ishiguro <kunihiro@ipinfusion.com>,
	Mitsuru KANDA <mk@linux-ipv6.org>,
	lksctp-developers@lists.sourceforge.net,
	Andy Adamson <andros@umich.edu>, Bruce Fields <bfields@umich.edu>,
	netdev@oss.sgi.com, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] resource release cleanup in net/
Date: Sat, 30 Apr 2005 18:26:45 -0300	[thread overview]
Message-ID: <39e6f6c705043014264eb4c0c5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0504302219520.2094@dragon.hyggekrogen.localhost>

On 4/30/05, Jesper Juhl <juhl-lkml@dif.dk> wrote:
> Hi David,
> 
> Since Andrew merged the patch that makes calling crypto_free_tfm() with a
> NULL pointer safe into 2.6.12-rc3-mm1, I made a patch to remove checks for
> NULL before calling that function, and while I was at it I removed similar
> redundant checks before calls to kfree() and vfree() in the same files.
> There are also a few tiny whitespace cleanups in there.

Jesper, I'd suggest that you left whitespaces for a separate patch, it
is always,
IMHO, better to have as small a patch as possible for reviewing.

- Arnaldo

  reply	other threads:[~2005-04-30 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 20:36 [PATCH] resource release cleanup in net/ Jesper Juhl
2005-04-30 21:26 ` Arnaldo Carvalho de Melo [this message]
2005-05-01  1:46   ` [PATCH 0/4] resource release cleanup in net/ (take 2) Jesper Juhl
2005-05-01  1:48     ` [PATCH 1/4] " Jesper Juhl
2005-05-01  1:50     ` [PATCH 2/4] " Jesper Juhl
2005-05-01  1:52     ` [PATCH 3/4] " Jesper Juhl
2005-05-01  1:55     ` [PATCH 4/4] " Jesper Juhl
2005-05-01  2:09       ` YOSHIFUJI Hideaki / 吉藤英明
2005-05-01  2:14         ` Jesper Juhl
2005-05-01  2:53 ` [PATCH] resource release cleanup in net/ Alexey Dobriyan
2005-04-30 23:13   ` Jesper Juhl
2005-05-01 12:32     ` Alexey Dobriyan
2005-05-01 23:08 ` Herbert Xu
2005-05-01 23:21   ` 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=39e6f6c705043014264eb4c0c5@mail.gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=andros@umich.edu \
    --cc=bfields@umich.edu \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jkmaline@cc.hut.fi \
    --cc=jmorris@intercode.com.au \
    --cc=juhl-lkml@dif.dk \
    --cc=kunihiro@ipinfusion.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=lksctp-developers@lists.sourceforge.net \
    --cc=mk@linux-ipv6.org \
    --cc=netdev@oss.sgi.com \
    --cc=roque@di.fc.ul.pt \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.