From: David Howells <dhowells@redhat.com>
To: Julia Lawall <julia@diku.dk>
Cc: dhowells@redhat.com, akinobu.mita@gmail.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/14] arch/frv: Eliminate NULL test and memset after alloc_bootmem
Date: Tue, 24 Jun 2008 10:21:16 +0000 [thread overview]
Message-ID: <7115.1214302876@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806241021080.26777@ask.diku.dk>
Julia Lawall <julia@diku.dk> wrote:
> As noted by Akinobu Mita in patch b1fceac2b9e04d278316b2faddf276015fc06e3b,
> alloc_bootmem and related functions never return NULL and always return a
> zeroed region of memory. Thus a NULL test or memset after calls to these
> functions is unnecessary.
Acked-by: David Howells <dhowells@redhat.com>
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Julia Lawall <julia@diku.dk>
Cc: dhowells@redhat.com, akinobu.mita@gmail.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/14] arch/frv: Eliminate NULL test and memset after alloc_bootmem
Date: Tue, 24 Jun 2008 11:21:16 +0100 [thread overview]
Message-ID: <7115.1214302876@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806241021080.26777@ask.diku.dk>
Julia Lawall <julia@diku.dk> wrote:
> As noted by Akinobu Mita in patch b1fceac2b9e04d278316b2faddf276015fc06e3b,
> alloc_bootmem and related functions never return NULL and always return a
> zeroed region of memory. Thus a NULL test or memset after calls to these
> functions is unnecessary.
Acked-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2008-06-24 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 8:21 [PATCH 2/14] arch/frv: Eliminate NULL test and memset after Julia Lawall
2008-06-24 8:21 ` [PATCH 2/14] arch/frv: Eliminate NULL test and memset after alloc_bootmem Julia Lawall
2008-06-24 10:21 ` David Howells [this message]
2008-06-24 10:21 ` David Howells
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=7115.1214302876@redhat.com \
--to=dhowells@redhat.com \
--cc=akinobu.mita@gmail.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@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 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.