All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Linux Edac Mailing List <linux-edac@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update EDAC information
Date: Sun, 1 Apr 2012 11:26:16 +0200	[thread overview]
Message-ID: <20120401092616.GB15717@aftab> (raw)
In-Reply-To: <201203311350.q2VDoO23007327@farm-0012.internal.tilera.com>

On Sat, Mar 31, 2012 at 09:46:03AM -0400, Chris Metcalf wrote:
> The bluesmoke mailing list no longer works, so use
> linux-edac@vger.kernel.org.  And, use a less restrictive pattern so all
> drivers/edac changes go to linux-edac as well.
> 
> Borislav suggested I just push this through the tile tree since there
> is currently no core edac maintainer (emails to Doug Thompson bounce).
> 
> Reviewed-by: Borislav Petkov <bp@amd64.org>
> Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>

Please don't add Reviewed-by tags to a patch which actually hasn't been
reviewed yet, no matter how trivial it is.

Other than that:

Acked-by: Borislav Petkov <bp@amd64.org>

Thanks for doing that.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

  reply	other threads:[~2012-04-01  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.285955.1333149246.6384.bluesmoke-devel@lists.sourceforge.net>
     [not found] ` <4F7642A9.2070801@tilera.com>
     [not found]   ` <20120331100214.GA7256@aftab>
2012-03-31 13:46     ` [PATCH] MAINTAINERS: update EDAC information Chris Metcalf
2012-04-01  9:26       ` Borislav Petkov [this message]
2012-04-01 16:26         ` Chris Metcalf

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=20120401092616.GB15717@aftab \
    --to=bp@amd64.org \
    --cc=cmetcalf@tilera.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.