From: "H. Peter Anvin" <hpa@zytor.com>
To: "David S. Miller" <davem@davemloft.net>,
James Bottomley <jejb@parisc-linux.org>,
Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Colin Watson <cjwatson@ubuntu.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-efi mailing list on vger
Date: Wed, 27 Jun 2012 11:08:47 -0700 [thread overview]
Message-ID: <4FEB4C2F.40205@zytor.com> (raw)
There are a lot of people working on EFI now, and there seems to be not
enough coordination.
Could we perhaps get a linux-efi@vger.kernel.org mailing list for this
stuff?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next reply other threads:[~2012-06-27 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 18:08 H. Peter Anvin [this message]
2012-06-27 18:32 ` linux-efi mailing list on vger James Bottomley
2012-06-27 22:08 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-06-28 9:20 Chris Jones
2012-06-28 15:20 ` 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=4FEB4C2F.40205@zytor.com \
--to=hpa@zytor.com \
--cc=cjwatson@ubuntu.com \
--cc=davem@davemloft.net \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).