linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Silvio Fricke <silvio.fricke@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Silvio Fricke <silvio.fricke@gmail.com>
Subject: [PATCH 00/11] using of calloc instead of malloc+memset
Date: Tue, 29 Sep 2015 19:10:35 +0200	[thread overview]
Message-ID: <cover.1443546000.git.silvio.fricke@gmail.com> (raw)
In-Reply-To: <cover.1443459879.git.silvio.fricke@gmail.com>

Hi btrfs,

please review my patches about switching from malloc with memset to calloc.
Thanks for that and eventual inclusion of my patches.

Silvio

Silvio Fricke (11):
  btrfs-progs: use calloc instead of malloc+memset for btrfs-image.c
  btrfs-progs: use calloc instead of malloc+memset for btrfs-list.c
  btrfs-progs: use calloc instead of malloc+memset for chunk-recover.c
  btrfs-progs: use calloc instead of malloc+memset for cmds-check.c
  btrfs-progs: use calloc instead of malloc+memset for disk-io.c
  btrfs-progs: use calloc instead of malloc+memset for extent_io.c
  btrfs-progs: use calloc instead of malloc+memset for mkfs.c
  btrfs-progs: use calloc instead of malloc+memset for qgroup.c
  btrfs-progs: use calloc instead of malloc+memset for quick-test.c
  btrfs-progs: use calloc instead of malloc+memset for volumes.c
  btrfs-progs: check: fix memset range

 btrfs-image.c   |  3 +--
 btrfs-list.c    |  9 +++------
 chunk-recover.c |  6 ++----
 cmds-check.c    | 12 ++++--------
 disk-io.c       |  7 ++-----
 extent_io.c     |  3 +--
 mkfs.c          |  3 +--
 qgroup.c        |  9 +++------
 quick-test.c    |  3 +--
 volumes.c       |  3 +--
 10 files changed, 19 insertions(+), 39 deletions(-)

-- 
2.5.3


       reply	other threads:[~2015-09-29 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1443459879.git.silvio.fricke@gmail.com>
2015-09-29 17:10 ` Silvio Fricke [this message]
2015-09-30 16:48   ` [PATCH 00/11] using of calloc instead of malloc+memset David Sterba
2015-09-30 16:54   ` David Sterba
2015-09-29 17:10 ` [PATCH 01/11] btrfs-progs: use calloc instead of malloc+memset for btrfs-image.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 02/11] btrfs-progs: use calloc instead of malloc+memset for btrfs-list.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 03/11] btrfs-progs: use calloc instead of malloc+memset for chunk-recover.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 04/11] btrfs-progs: use calloc instead of malloc+memset for cmds-check.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 05/11] btrfs-progs: use calloc instead of malloc+memset for disk-io.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 06/11] btrfs-progs: use calloc instead of malloc+memset for extent_io.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 07/11] btrfs-progs: use calloc instead of malloc+memset for mkfs.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 08/11] btrfs-progs: use calloc instead of malloc+memset for qgroup.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 09/11] btrfs-progs: use calloc instead of malloc+memset for quick-test.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 10/11] btrfs-progs: use calloc instead of malloc+memset for volumes.c Silvio Fricke
2015-09-29 17:10 ` [PATCH 11/11] btrfs-progs: check: fix memset range Silvio Fricke

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=cover.1443546000.git.silvio.fricke@gmail.com \
    --to=silvio.fricke@gmail.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).