From: Sam Ravnborg <sam@ravnborg.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>, akpm <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/slab: add kernel-doc for one function
Date: Sun, 22 Jan 2006 22:19:26 +0100 [thread overview]
Message-ID: <20060122211926.GB13980@mars.ravnborg.org> (raw)
In-Reply-To: <20060122204507.GA11002@admingilde.org>
On Sun, Jan 22, 2006 at 09:45:07PM +0100, Martin Waitz wrote:
> hoi :)
>
> thanks, I applied all three patches to
> http://tali.admingilde.org/git/linux-docbook.git,
> and I guess Andrew will take care of merging them with Linus.
That is the responsibility of the subsystem maintainer - as you have
become now.
At least in the normal case Andrew suck in the git trees and leave it to
the git tree owners to push to Linus.
It's a bit different compared to when you just sent patches to Andrew.
Sam
next prev parent reply other threads:[~2006-01-22 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 4:37 [PATCH] mm/slab: add kernel-doc for one function Randy.Dunlap
2006-01-22 20:45 ` Martin Waitz
2006-01-22 21:19 ` Sam Ravnborg [this message]
2006-01-22 21:51 ` Martin Waitz
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=20060122211926.GB13980@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.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;
as well as URLs for NNTP newsgroup(s).