public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <borislav.petkov@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: edac-amd tree (Was: Re: linux-next: Tree for November 16)
Date: Tue, 17 Nov 2009 13:00:13 +0100	[thread overview]
Message-ID: <20091117120013.GC14954@aftab> (raw)
In-Reply-To: <20091117141935.18a8ed94.sfr@canb.auug.org.au>

Hi Stephen,

On Tue, Nov 17, 2009 at 02:19:35PM +1100, Stephen Rothwell wrote:
> Added back from today.

thanks.

> Just in case I missed you last time:

you didn't but no worries, see below:

> You will need to ensure that the patches/commits in your tree/series have
> been:
>      * submitted under GPL v2 (or later) and include the Contributor's
> 	Signed-off-by,

yes

>      * posted to the relevant mailing list,

yes

>      * reviewed by you (or another maintainer of your subsystem tree),

in progress

>      * successfully unit tested, and 

yes

>      * destined for the current or next Linux merge window.

and yes.

Thanks.

-- 
Regards/Gruss,
Boris.

Operating | Advanced Micro Devices GmbH
  System  | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
 Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
  Center  | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
  (OSRC)  | Registergericht München, HRB Nr. 43632


  reply	other threads:[~2009-11-17 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16  7:14 linux-next: Tree for November 16 Stephen Rothwell
2009-11-16 14:32 ` Borislav Petkov
2009-11-17  3:19   ` edac-amd tree (Was: Re: linux-next: Tree for November 16) Stephen Rothwell
2009-11-17 12:00     ` Borislav Petkov [this message]
2009-11-16 23:32 ` [PATCH -next] acpi: get_bios_limit static inline when CPU_FREQ=n Randy Dunlap
2009-11-16 23:32 ` [PATCH -next] x86/cpufreq: don't use acpi_processor_get_bios_limit when not available Randy Dunlap

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=20091117120013.GC14954@aftab \
    --to=borislav.petkov@amd.com \
    --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