From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: [PATCH] Fix numerous kcalloc() calls, convert to kzalloc().
Date: Sat, 09 Dec 2006 23:05:58 +0100 [thread overview]
Message-ID: <457B3346.2020008@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0612090950580.14897@localhost.localdomain>
Robert P. J. Day wrote:
> drivers/ata/pdc_adma.c | 4 ++--
> drivers/macintosh/smu.c | 2 +-
> drivers/mtd/rfd_ftl.c | 2 +-
> drivers/net/phy/phy_device.c | 2 +-
> drivers/net/skge.c | 2 +-
> drivers/pcmcia/at91_cf.c | 2 +-
> drivers/pcmcia/omap_cf.c | 2 +-
> drivers/pnp/isapnp/core.c | 22 +++++++++++-----------
> drivers/pnp/pnpacpi/core.c | 6 +++---
> drivers/pnp/pnpacpi/rsparser.c | 22 +++++++++++-----------
> drivers/pnp/pnpbios/core.c | 14 +++++++-------
> drivers/pnp/pnpbios/proc.c | 8 ++++----
> drivers/pnp/pnpbios/rsparser.c | 16 ++++++++--------
> drivers/scsi/sym53c8xx_2/sym_hipd.c | 2 +-
> drivers/usb/gadget/at91_udc.c | 2 +-
> drivers/usb/misc/uss720.c | 2 +-
> drivers/usb/net/rndis_host.c | 2 +-
> fs/ocfs2/alloc.c | 2 +-
> fs/ocfs2/cluster/heartbeat.c | 4 ++--
> fs/ocfs2/cluster/nodemanager.c | 6 +++---
> fs/ocfs2/cluster/tcp.c | 10 +++++-----
> fs/ocfs2/dlm/dlmdomain.c | 4 ++--
> fs/ocfs2/dlm/dlmlock.c | 4 ++--
> fs/ocfs2/dlm/dlmmaster.c | 2 +-
> fs/ocfs2/dlm/dlmrecovery.c | 6 +++---
> fs/ocfs2/localalloc.c | 2 +-
> fs/ocfs2/slot_map.c | 2 +-
> fs/ocfs2/suballoc.c | 6 +++---
> fs/ocfs2/super.c | 6 +++---
> fs/ocfs2/vote.c | 4 ++--
> include/linux/gameport.h | 2 +-
> kernel/relay.c | 4 ++--
> net/sunrpc/svc.c | 2 +-
> sound/pci/hda/patch_realtek.c | 4 ++--
> 34 files changed, 91 insertions(+), 91 deletions(-)
This should really be split up and submitted separately. All the subsystems
are constantly changing. Although merging these kinds of changes manually
after eventual conflicts, it's still manual work for the maintainers which
would be avoided by a little bit extra work by the submitter. A maintainer
could get a merge conflict on a 100 lines long hunk because of an 8 lines
long hunk that got upstream on a different route.
--
Stefan Richter
-=====-=-==- ==-- -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-12-09 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 14:54 Robert P. J. Day
2006-12-09 22:05 ` Stefan Richter [this message]
2006-12-09 22:10 ` Robert P. J. Day
2006-12-09 23:07 ` Stefan Richter
2006-12-09 22:30 ` Andrew Morton
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=457B3346.2020008@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®