Re: linux-next: Tree for May 15

From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Doug Thompson <dougthompson@xmission.com>
Subject: Re: linux-next: Tree for May 15
Date: Mon, 18 May 2009 00:07:34 +1000	[thread overview]
Message-ID: <20090518000734.6fd3d652.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090515130729.GA13026@aftab>

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

Hi Boris,

On Fri, 15 May 2009 15:07:29 +0200 Borislav Petkov <borislav.petkov@amd.com> wrote:
>
> can you please add the tree at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git for-next
> 
> to linux-test for a wider testing. It is rebased ontop of
> 45d447406a19cbfd42720f066f156f4eb9d68801 (Linus's tree from yesterday).

A hint as to what the tree is about would be nice.  It looks like EDAC
stuff (mostly AMD64).  If so, you are not listed as a maintainer of that
code (Doug cc'd).

The boilerplate:

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 --]