Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>, jdmason@kudzu.us
Cc: kexec@lists.infradead.org, horms@verge.net.au,
	ebiederm@xmission.com, dyoung@redhat.com,
	Thomas Renninger <trenn@suse.de>, WANG Chao <chaowang@redhat.com>
Subject: Re: [PATCH v2 0/4] kexec-tools, x86: E820 memmap pass for kdump
Date: Mon, 24 Feb 2014 07:28:02 -0800	[thread overview]
Message-ID: <c264cd10-2c97-4f03-bb8d-c6ba018ecc03@email.android.com> (raw)
In-Reply-To: <20140224152427.GD4631@redhat.com>

I think Muli had moved on a while ago.

On February 24, 2014 7:24:27 AM PST, Vivek Goyal <vgoyal@redhat.com> wrote:
>On Mon, Feb 24, 2014 at 10:11:03AM -0500, Vivek Goyal wrote:
>> On Mon, Feb 24, 2014 at 07:03:07AM -0800, H. Peter Anvin wrote:
>> > First question is if Calgary even exists anymore and if so if
>someone actually cares about it enough to maintain it.
>> 
>> Atleast MAINTAINERS file says it is maintained.
>> 
>> CALGARY x86-64 IOMMU
>> M:      Muli Ben-Yehuda <muli@il.ibm.com>
>> M:      "Jon D. Mason" <jdmason@kudzu.us>
>> L:      discuss@x86-64.org
>> S:      Maintained
>> F:      arch/x86/kernel/pci-calgary_64.c
>> F:      arch/x86/kernel/tce_64.c
>> F:      arch/x86/include/asm/calgary.h
>> F:      arch/x86/include/asm/tce.h
>> 
>> 
>> I am add maintainers to CC list and they can shed more light on if
>> calgary still exists and if somebody actually cares about it.
>
>Jon,
>
>Muli's mail is bouncing. Is he still maintaining calgary and is his
>mail id still valid as mentioned in MAINTAINERS entry above.
>
>Thanks
>Vivek

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-02-24 15:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  9:28 [PATCH v2 0/4] kexec-tools, x86: E820 memmap pass for kdump WANG Chao
2014-02-20  9:28 ` [PATCH v2 1/4] cleanup: add dbgprint_mem_range function WANG Chao
2014-02-20  9:28 ` [PATCH v2 2/4] x86: Store memory ranges globally used for crash kernel to boot into WANG Chao
2014-02-20  9:28 ` [PATCH v2 3/4] x86: add --pass-memmap-cmdline option WANG Chao
2014-02-20  9:28 ` [PATCH v2 4/4] x86: Pass memory range via E820 for kdump WANG Chao
2014-02-27 20:53   ` Linn Crosetto
2014-02-28  8:32     ` WANG Chao
2014-02-24 10:38 ` [PATCH v2 0/4] kexec-tools, x86: E820 memmap pass " Thomas Renninger
2014-02-24 14:58   ` WANG Chao
2014-02-24 15:03     ` H. Peter Anvin
2014-02-24 15:11       ` Vivek Goyal
2014-02-24 15:24         ` Vivek Goyal
2014-02-24 15:28           ` H. Peter Anvin [this message]
2014-02-24 15:22     ` Vivek Goyal
2014-02-24 15:27       ` H. Peter Anvin
2014-02-24 15:34       ` Thomas Renninger
2014-02-24 15:45         ` Vivek Goyal
2014-02-24 15:50           ` H. Peter Anvin
2014-02-24 15:59             ` Vivek Goyal

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=c264cd10-2c97-4f03-bb8d-c6ba018ecc03@email.android.com \
    --to=hpa@zytor.com \
    --cc=chaowang@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=jdmason@kudzu.us \
    --cc=kexec@lists.infradead.org \
    --cc=trenn@suse.de \
    --cc=vgoyal@redhat.com \
    /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