linux-kernel - Re: [PATCH 2.6.20-rc3] DAC960: kmalloc->kzalloc/Casting cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 6 Jan 2007 08:36:23 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	"Ahmed S. Darwish" <darwish.07@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.20-rc3] DAC960: kmalloc->kzalloc/Casting cleanups

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@...il.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/