From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: abonilla@linuxwireless.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch Question.
Date: Wed, 21 Sep 2005 21:32:19 -0700 [thread overview]
Message-ID: <20050921213219.090d63c5.rdunlap@xenotime.net> (raw)
In-Reply-To: <1127358091.5644.7.camel@localhost.localdomain>
On Wed, 21 Sep 2005 21:01:31 -0600 Alejandro Bonilla Beeche wrote:
> Hi,
>
> I have a couple of questions about sending patches. I did read the
> SubmittingPatches Doc but don't recall this.
>
> Can anyone send a patch to LKML to be applied?
Anyone can send a patch. Whether it gets applied depends on
several factors.
> How long does it normally take for a patch to be merged?
Depends on who you ask to merge it. Andrew put patches into
the -mm patchset within minutes sometimes, depending on how
busy he is, what else he is doing, etc.
But it varies quite a bit by driver or subsystem maintainer.
> If a patch is not merged and I get no Replys, what should one do?
Send it to the correct maintainer (driver or subsystem usually).
If you can't find a correct maintainer, then send it to Andrew
(akpm@osdl.org). Maybe put "[RFC]" in the Subject: line to
get (more) comments on it.
---
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law
next prev parent reply other threads:[~2005-09-22 4:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 3:01 Patch Question Alejandro Bonilla Beeche
2005-09-22 4:32 ` Randy.Dunlap [this message]
2005-09-22 6:33 ` Jesper Juhl
2017-04-17 23:28 Perry Hooker
2017-04-17 23:48 ` Mandeep Sandhu
2017-04-17 23:58 ` Tobin C. Harding
2017-04-18 23:07 ` Perry Hooker
2017-04-19 0:11 ` Tobin C. Harding
2017-04-19 15:54 ` Perry Hooker
2017-04-19 16:13 ` Greg KH
2017-04-19 16:46 ` Perry Hooker
2017-04-19 20:48 ` Lino Sanfilippo
2017-04-19 13:27 ` Lino Sanfilippo
2017-04-19 15:41 ` Perry Hooker
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=20050921213219.090d63c5.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=abonilla@linuxwireless.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.