public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Burman Yan <yan_952@hotmail.com>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATH] Replace kmalloc+memset with kzalloc 1/17
Date: Mon, 13 Nov 2006 12:51:43 +0000	[thread overview]
Message-ID: <45586A5F.4040304@grupopie.com> (raw)
In-Reply-To: <BAY20-F24A945741EAE00E4980CEAD8F50@phx.gbl>

Burman Yan wrote:
> OK.
> Sorry.
> 
> I had to attach the patch, since hotmail does line wrapping, but I will 
> note the part regarding
> the more descriptive subject.

Hotmail is probably the _worse_ email client you could use to send 
patches to the kernel.

> Also, some of the patches are one line per file, so I joined them 
> together in one single patch.
> I thought that splitting that into many tiny patches will actually be 
> more annoying than
> a single bigger patch.

The logical separation you did isn't bad, but there is no mention on the 
*subject line* what section is targeted by your patch.

Also you should CC the maintainer for each section you're targeting. For 
instance, for the ACPI patch you should also CC Len Brown. Check the 
MAINTAINERS file for the right people to CC on each patch.

> Does that mean I should send those patches again?

Afraid so.

While you're at it, you could remove casts like this one:

-	pathname = (char *)kmalloc(ACPI_PATHNAME_MAX, GFP_KERNEL);
+	pathname = (char *)kzalloc(ACPI_PATHNAME_MAX, GFP_KERNEL);
  	if (!pathname)
  		return -ENOMEM;
-	memset(pathname, 0, ACPI_PATHNAME_MAX);

That "(char *)" really isn't needed.

Oh, and just one more thing: don't top post.

-- 
Paulo Marques - www.grupopie.com

"The face of a child can say it all, especially the
mouth part of the face."

      reply	other threads:[~2006-11-13 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 17:20 [PATH] Replace kmalloc+memset with kzalloc 1/17 Burman Yan
2006-11-12 17:31 ` Russell King
2006-11-12 18:25   ` Randy Dunlap
2006-11-12 21:40     ` Jan Engelhardt
2006-11-12 19:36   ` Burman Yan
2006-11-13 12:51     ` Paulo Marques [this message]

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=45586A5F.4040304@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=yan_952@hotmail.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