LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Ahmed S. Darwish" <darwish.07@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.20-rc3] DAC960: kmalloc->kzalloc/Casting cleanups
Date: Sat, 6 Jan 2007 08:36:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701060833150.12420@localhost.localdomain> (raw)
In-Reply-To: <20070106131725.GB19020@Ahmed>

On Sat, 6 Jan 2007, Ahmed S. Darwish wrote:

> Hi all,
> I'm not able to find the DAC960 block driver maintainer. If someones knows
> please reply :).
>
> A patch to switch kmalloc->kzalloc and to clean unneeded kammloc,
> pci_alloc_consistent casts
>
> Signed-off-by: Ahmed Darwish <darwish.07@gmail.com>
>
> diff --git a/drivers/block/DAC960.c b/drivers/block/DAC960.c

  a couple bits of advice here.  you should start your patch
submission with *only* that descriptive text you want included in the
log, followed by your "Signed-off-by" line, then a line containing
"---".

  *after* that "---" line, and *before* you start the actual patch,
you can add superfluous text, like asking about who the maintainer is,
so that informal dialogue like that doesn't become part of the
permanent patch record.

  in short, your patch should look like:

A patch to switch...

Signed-off-by: ...

---

  i'm not sure who the maintainer is.  can anyone help?

diff --git ...



rday

  reply	other threads:[~2007-01-06 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06 13:17 Ahmed S. Darwish
2007-01-06 13:36 ` Robert P. J. Day [this message]
2007-01-06 14:55   ` Ahmed S. Darwish
2007-01-06 17:46 ` Randy Dunlap
2007-01-07  2:00   ` Ahmed S. Darwish
2007-01-07  2:31     ` Randy Dunlap
2007-01-07  2:38     ` Alan
2007-01-07  2:48     ` Jesper Juhl
2007-01-07  2:49     ` Jesper Juhl
2007-01-08 10:09 ` Toon van der Pas

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=Pine.LNX.4.64.0701060833150.12420@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=darwish.07@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH 2.6.20-rc3] DAC960: kmalloc->kzalloc/Casting cleanups' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox