From: Randy Dunlap <randy.dunlap@oracle.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 18:31:30 -0800 [thread overview]
Message-ID: <20070106183130.09d08218.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070107020010.GH19020@Ahmed>
On Sun, 7 Jan 2007 04:00:10 +0200 Ahmed S. Darwish wrote:
> On Sat, Jan 06, 2007 at 09:46:30AM -0800, Randy Dunlap wrote:
>
> > On Sat, 6 Jan 2007 15:17:25 +0200 Ahmed S. Darwish wrote:
> >
> > > Hi all,
> > > I'm not able to find the DAC960 block driver maintainer. If someones knows
> > > please reply :).
> >
> > It's orphaned. Andrew can decide to merge this, or one of the
> > storage or block maintainers could possibly do that.
> > or it could go thru KJ, but then Andrew may still end up
> > merging it.
>
> Should Kernel janitors then care of cleaning orphaned files ?.
Kernel janitors could do that (IMO). It's up to you where you want
to send the patch.
> If so, I should forward it to Andrew Morton without CCing LKML again, right ?
I would expect that Andrew has seen the patch. Anyway, you should
always send the patch to a mailing list and usually to a specific
maintainer also (like Andrew or a subsystem maintainer or the KJ
maintainer). [except for some security-related patches]
---
~Randy
next prev parent reply other threads:[~2007-01-07 2:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 13:17 [PATCH 2.6.20-rc3] DAC960: kmalloc->kzalloc/Casting cleanups Ahmed S. Darwish
2007-01-06 13:36 ` Robert P. J. Day
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 [this message]
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=20070106183130.09d08218.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=darwish.07@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).