From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Simon Guinot <simon.guinot@sequanux.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH v3] gpio: add GPIO support for F71882FG and F71889F
Date: Thu, 29 Aug 2013 23:22:19 +0100 [thread overview]
Message-ID: <20130829222219.GA24221@srcf.ucam.org> (raw)
In-Reply-To: <20130829222053.GE13942@kw.sim.vm.gnt>
On Fri, Aug 30, 2013 at 12:20:54AM +0200, Simon Guinot wrote:
> Almost all the LaCie NASes are running a Linux based OS. I can assure
> you that LaCie really takes care of Linux. Now, the main reason why the
> Super-I/O ACPI support is missing on this boards is a lack of knowledge.
> Thanks to this discussion, I am now aware of that. Then, for the next
> products, I will do my best to get AMLs or at least ACPI IDs.
Awesome! Let me know if you need any advice on this.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-08-29 22:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 9:50 [PATCH v3] gpio: add GPIO support for F71882FG and F71889F Simon Guinot
2013-07-29 15:59 ` Linus Walleij
2013-07-29 20:26 ` Rafael J. Wysocki
2013-08-01 13:46 ` Simon Guinot
2013-08-01 15:52 ` Guenter Roeck
2013-08-26 15:15 ` Simon Guinot
2013-08-29 12:39 ` Linus Walleij
2013-08-29 12:57 ` Matthew Garrett
2013-08-29 13:41 ` Guenter Roeck
2013-08-29 15:37 ` Matthew Garrett
2013-08-29 16:08 ` Guenter Roeck
2013-08-29 16:25 ` Matthew Garrett
2013-08-29 17:31 ` Guenter Roeck
2013-08-29 22:20 ` Simon Guinot
2013-08-29 22:22 ` Matthew Garrett [this message]
2013-08-29 17:32 ` Linus Walleij
2013-08-29 17:35 ` Linus Walleij
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=20130829222219.GA24221@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=grant.likely@secretlab.ca \
--cc=hpa@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rjw@sisk.pl \
--cc=simon.guinot@sequanux.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.