public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: abonilla@linuxwireless.org
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: Patch Question.
Date: Thu, 22 Sep 2005 08:33:39 +0200	[thread overview]
Message-ID: <9a8748490509212333197a4980@mail.gmail.com> (raw)
In-Reply-To: <20050921213219.090d63c5.rdunlap@xenotime.net>

On 9/22/05, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> 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.
>
Also depends on the content of the patch. If it is tricky to read/non
obvious etc it will usually draw some comments before being merged.
Some patches get missed/overlooked completely - in that case it's up
to you to make sure it gets resend after a while (if it draws no
comments and doesn't get merged, then resending it after the next
majoe, -rc or -mm release, updated to apply to that release, is
usually good).
I've personally sent patches that got merged by someone within a few
minutes, but I've also seen patches suddenly get merged that I had
completely forgotten about that some maintainer just picked up from
the list weeks after I had sent it.


> > 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.
>
Resend the patch and check your To: and Cc: lists. Read the
MAINTAINERS file to find out who to send it to, as well as comments in
the top of the source file. Adding linux-kernel@vger.kernel.org to Cc:
in any case, in addition to other recipients, is usually a good thing
as well.


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      reply	other threads:[~2005-09-22  6:33 UTC|newest]

Thread overview: 3+ 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
2005-09-22  6:33   ` Jesper Juhl [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=9a8748490509212333197a4980@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=abonilla@linuxwireless.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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