From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Michal Marek <mmarek@suse•cz>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
matt mooney <mfm@muteddisk•com>, Kirill Smelkov <kirr@mns•spb.ru>
Subject: Re: linux-next: manual merge of the kbuild tree with the kernel-doc tree
Date: Thu, 27 May 2010 09:09:23 +1000 [thread overview]
Message-ID: <20100527090923.c17a7ed4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100526095606.beed820e.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hi Randy,
On Wed, 26 May 2010 09:56:06 -0700 Randy Dunlap <randy.dunlap@oracle•com> wrote:
>
> > The kernel-doc tree is a quilt series :-(
>
> Yes. and it's viewable without pulling/cloning. ;)
Ah, I shouldn't reply to emails so late at night :-(
> > You can, of course, see the above commit in the linux-next tree via
> > gitweb on kernel.org.
>
> Thanks. Michal, I droppped these 3 patches. Please keep them in the
> kbuild tree.
If anything, the kernel-doc patches should be kept as they are much more
extensive. And the conflict was trivial. The kbuild patch was just
fixing a typo (tey -> they).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-26 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 1:53 linux-next: manual merge of the kbuild tree with the kernel-doc tree Stephen Rothwell
2010-05-26 15:47 ` Randy Dunlap
2010-05-26 16:50 ` Stephen Rothwell
2010-05-26 16:56 ` Randy Dunlap
2010-05-26 23:09 ` Stephen Rothwell [this message]
2010-05-27 0:00 ` Randy Dunlap
2010-05-27 1:03 ` Stephen Rothwell
2010-05-27 14:16 ` Michal Marek
2010-05-27 15:34 ` Stephen Rothwell
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=20100527090923.c17a7ed4.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=kirr@mns$(echo .)spb.ru \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mfm@muteddisk$(echo .)com \
--cc=mmarek@suse$(echo .)cz \
--cc=randy.dunlap@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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