From: mjg59@srcf.ucam.org (Matthew Garrett)
To: linux-arm-kernel@lists.infradead.org
Subject: ACPI
Date: Sun, 24 Nov 2013 03:56:51 +0000 [thread overview]
Message-ID: <20131124035651.GA7580@srcf.ucam.org> (raw)
In-Reply-To: <2940EDD8-0EE7-4D61-96F7-3D78D5A52644@jonmasters.org>
On Sat, Nov 23, 2013 at 10:52:25PM -0500, Jon Masters wrote:
> Matthew, good points! Suffice it to say many productive conversations
> have occurred recently with regard to openness. I am constrained
> indeed, and somewhat willingly because that is the only way to engage
> with everyone who might (or might not) be involved in the ARM
> ecosystem in the timeframe that will matter in the medium/longer term
> (this is a decade+ long story). As you know, I'm a huge fan of
> standards (especially openly published ones), and in particular of
> having one way to do things that will work for an entire ecosystem
> (beyond just Linux), because that's how we get to an open platform
> that anyone can target. That's not the natural course things would
> take without steering. In the ARM space, the natural course might be
> to create vertical solutions that, while awesome, are harder to target
> with a general purpose one-size-fits-all OS story. I'll look forward
> to seeing more announcements coming soon.
That seems to be a very verbose way to say "We have no plans to make
sure this is going to work for upstream Linux". I'm disappointed to see
Red Hat play along with this.
--
Matthew Garrett | mjg59 at srcf.ucam.org
next prev parent reply other threads:[~2013-11-24 3:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 18:42 ACPI Jon Masters
[not found] ` < CACRpkdY+6dzs8MpKKtW-3kzsLkZjsit9SeN20k_33TAtVf3NEA@mail.gmail.com>
[not found] ` < CACxGe6t_9hUXL_1PHRU=2DYOYfCqZykd7gYRCshZn0XsVoCdRw@mail.gmail.com>
[not found] ` < 20131126183344.GA16074@srcf.ucam.org>
[not found] ` < CACRpkdbNxxNK0GM28H_nDLu6EpbQ-EYAdEeTp5fnXW5mkEPkgw@mail.gmail.com>
[not found] ` < CACxGe6uHuWPh7d9NaVuPRBWq0Fh1BmDV190KEN4C4uaq4KjS8g@mail.gmail.com>
[not found] ` < CACRpkdaCXJzWXoesjD3Jqpm4XMHLQp3SsHcsDG3veUS+xarqHQ@mail.gmail.com>
[not found] ` < CACxGe6vUKzow7QpeX2mU7CiZQzY8aZ+p0jd8Vk0+dqz0B=D0Ew@mail.gmail.com>
2013-11-19 18:15 ` ACPI Arnd Bergmann
2013-11-21 20:03 ` ACPI Mark Brown
2013-11-22 0:29 ` ACPI Arnd Bergmann
2013-11-22 4:05 ` ACPI Jon Masters
2013-11-22 20:31 ` ACPI Arnd Bergmann
2013-11-22 20:59 ` ACPI Jon Masters
2013-11-22 21:37 ` ACPI Jon Masters
2013-11-23 9:11 ` ACPI Arnd Bergmann
2013-11-23 18:39 ` ACPI Jason Gunthorpe
2013-11-23 23:03 ` ACPI Matthew Garrett
2013-11-24 3:52 ` ACPI Jon Masters
2013-11-24 3:56 ` Matthew Garrett [this message]
2013-11-24 23:21 ` ACPI Jon Masters
2013-11-24 23:40 ` ACPI Matthew Garrett
2013-11-22 13:19 ` ACPI Mark Brown
2013-11-19 18:28 ` ACPI Måns Rullgård
2013-11-21 16:56 ` ACPI Matthew Garrett
2013-11-24 17:14 ` ACPI Linus Walleij
2013-11-25 0:42 ` ACPI Grant Likely
2013-11-25 1:28 ` ACPI Matthew Garrett
2013-11-25 11:07 ` ACPI Linus Walleij
2013-11-25 11:33 ` ACPI Grant Likely
2013-11-25 15:41 ` ACPI Matthew Garrett
2013-11-26 12:43 ` ACPI Linus Walleij
2013-11-26 12:55 ` ACPI Grant Likely
2013-11-26 13:43 ` ACPI Jürgen Beisert
2013-11-27 12:25 ` ACPI Grant Likely
2013-11-28 13:16 ` ACPI Linus Walleij
2013-11-26 18:33 ` ACPI Matthew Garrett
2013-11-26 23:11 ` ACPI Matt Sealey
2013-11-26 23:32 ` ACPI Matthew Garrett
2013-11-27 11:00 ` ACPI Catalin Marinas
2013-11-27 22:12 ` ACPI Nicolas Pitre
2013-11-27 20:21 ` ACPI Matt Sealey
2013-11-28 6:21 ` ACPI Jon Masters
2013-11-28 18:26 ` ACPI Stefano Stabellini
2013-11-28 18:48 ` ACPI Matthew Garrett
2013-11-28 18:51 ` ACPI Stefano Stabellini
2013-11-27 14:16 ` ACPI Grant Likely
2013-11-27 22:17 ` ACPI Matt Sealey
2013-11-28 13:50 ` ACPI Leif Lindholm
2013-11-28 15:43 ` ACPI Grant Likely
2013-11-27 12:41 ` ACPI Grant Likely
2013-11-26 14:45 ` ACPI Matthew Garrett
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=20131124035651.GA7580@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-arm-kernel@lists.infradead.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).