All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Amul Shah <amul.shah@unisys.com>,
	LKML <linux-kernel@vger.kernel.org>,
	cherry@osdl.org
Subject: Re: [RFC] [PATCH 2.6.19-rc4] kdump panics early in boot when  reserving MP Tables located in high memory
Date: Fri, 3 Nov 2006 13:51:15 -0500	[thread overview]
Message-ID: <20061103185115.GD13422@in.ibm.com> (raw)
In-Reply-To: <200611031943.48127.ak@suse.de>

On Fri, Nov 03, 2006 at 07:43:48PM +0100, Andi Kleen wrote:
> On Friday 03 November 2006 18:40, Vivek Goyal wrote:
> 
> > When did fastboot become a closed mailing list? AFAIK, its an open list
> > and anybody can do the posting.
> 
> It's been for a long time. At least I remember often getting these bounces.
> 

You are right. Just now I sent a mail to the administrator of the list and
he told that recently he made fastboot a closed list to avoid spams. But he
is now re-opening the list for everybody as we want to archive the
kexec/kdump related discussions in fastboot list. Finding a past discussion
on LKML is tough.

So now onwards you should not be receiving those annoying messages.

Thanks
Vivek

      reply	other threads:[~2006-11-03 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 22:24 [RFC] [PATCH 2.6.19-rc4] kdump panics early in boot when reserving MP Tables located in high memory Amul Shah
2006-11-02 23:36 ` [Fastboot] " Vivek Goyal
2006-11-03 14:30   ` Amul Shah
2006-11-03  2:40 ` Andi Kleen
2006-11-03 14:55   ` Amul Shah
2006-11-03 16:51     ` Andi Kleen
2006-11-03 17:17       ` Vivek Goyal
2006-11-03 19:47         ` Amul Shah
2006-11-03 19:52           ` Andi Kleen
2006-11-03 21:17             ` Amul Shah
2006-11-03 22:01               ` Andi Kleen
2006-11-03 17:40       ` Vivek Goyal
2006-11-03 18:43         ` Andi Kleen
2006-11-03 18:51           ` Vivek Goyal [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=20061103185115.GD13422@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=ak@suse.de \
    --cc=amul.shah@unisys.com \
    --cc=cherry@osdl.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.