From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Next <linux-next@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: A few tree inclusion update requests
Date: Sat, 10 Apr 2010 15:42:23 +0200 [thread overview]
Message-ID: <20100410134221.GC5204@nowhere> (raw)
Hi Stephen,
I have some requests for you about tree inclusions for linux-next.
My reiserfs/kill-bkl branch had no updates for a next release
for some time now. You can safely remove it from -next. If
I get updates for it later, I'll tell you. But for now it's
only here to host fixes for the current release.
Also I have two new branches aimed for .35
Could you please integrate the two following?
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
bkl/core
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
bkl/procfs
Thanks a lot!
next reply other threads:[~2010-04-10 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 13:42 Frederic Weisbecker [this message]
2010-04-12 23:46 ` A few tree inclusion update requests Stephen Rothwell
2010-04-27 2:55 ` Frederic Weisbecker
2010-04-27 5:10 ` Stephen Rothwell
2010-04-27 5:21 ` Frederic Weisbecker
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=20100410134221.GC5204@nowhere \
--to=fweisbec@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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