From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: Re: Merge request for kmemleak patches
Date: Tue, 28 Jul 2009 21:00:22 +1000 [thread overview]
Message-ID: <20090728210022.f5226f20.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1248772559.17665.12.camel@pc1117.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi Catalin,
On Tue, 28 Jul 2009 10:15:59 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> There are a few more kmemleak patches for the upcoming merging window
> (the first one will be pushed before). Could you please pull them into
> the -next tree? Thanks.
>
> git://linux-arm.org/linux-2.6.git kmemleak
I have added the tree back for tomorrow.
What I tell everyone: all patches/commits in the tree/series must
have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-28 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 9:15 Merge request for kmemleak patches Catalin Marinas
2009-07-28 11:00 ` Stephen Rothwell [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=20090728210022.f5226f20.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=catalin.marinas@arm.com \
--cc=linux-next@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 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).