From: James Bottomley <James.Bottomley@SteelEye.com>
To: akpm@linux-foundation.org
Cc: linux-scsi@vger.kernel.org, m.kozlowski@tuxland.pl
Subject: Re: [patch 20/30] drivers/scsi/gdth.c: kmalloc + memset conversion to kzalloc
Date: Fri, 10 Aug 2007 21:00:55 -0400 [thread overview]
Message-ID: <1186794055.6334.16.camel@localhost.localdomain> (raw)
In-Reply-To: <200708102150.l7ALokrZ011378@imap1.linux-foundation.org>
On Fri, 2007-08-10 at 14:50 -0700, akpm@linux-foundation.org wrote:
> From: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
>
> drivers/scsi/gdth.c | 189401 -> 189342 (-59 bytes)
> drivers/scsi/gdth.o | 331028 -> 330324 (-704 bytes)
For the second time of asking, could I just have a single patch doing
this globally for the entirety of SCSI with reasonable assurance of
mechanical checking.
There's no real need to collect maintainer acks for something as trivial
as this.
James
next prev parent reply other threads:[~2007-08-11 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 21:50 [patch 20/30] drivers/scsi/gdth.c: kmalloc + memset conversion to kzalloc akpm
2007-08-11 1:00 ` James Bottomley [this message]
2007-08-11 8:13 ` Mariusz Kozlowski
2007-08-11 16:26 ` James Bottomley
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=1186794055.6334.16.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
/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