From: Wolfram Sang <wsa@the-dreams.de>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: acooks@rationali.st, Jean Delvare <jdelvare@suse.de>,
Linux I2C <linux-i2c@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
platypus-sw@opengear.com, "Tobin C . Harding" <me@tobin.cc>,
Guenter Roeck <linux@roeck-us.net>,
Will Wagner <willw@carallon.com>
Subject: Re: [PATCH v5 0/3] Enable ACPI-defined peripherals on i2c-piix4 SMBus
Date: Mon, 19 Aug 2019 20:53:34 +0200 [thread overview]
Message-ID: <20190819185334.GA9762@kunai> (raw)
In-Reply-To: <9019cce9-837f-97fc-0f3b-7503b8fc3717@metux.net>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
Just so I get this correct: This is all about instantiating the devices
sitting on the SMBus, but you are okay with Jean's patches? Or is this
discussion affecting patch 3? (/me knows not much about ACPI'n'stuff)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-19 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 12:51 [PATCH v5 0/3] Enable ACPI-defined peripherals on i2c-piix4 SMBus Jean Delvare
2019-08-02 12:52 ` [PATCH v5 1/3] i2c: piix4: Fix port selection for AMD Family 16h Model 30h Jean Delvare
2019-08-29 20:19 ` Wolfram Sang
2019-08-02 12:54 ` [PATCH v5 2/3] i2c: piix4: Fix probing of reserved ports on " Jean Delvare
2019-08-29 20:20 ` Wolfram Sang
2019-08-02 12:55 ` [PATCH v5 3/3] i2c: piix4: Add ACPI support Jean Delvare
2019-08-29 20:21 ` Wolfram Sang
2019-08-08 9:17 ` [PATCH v5 0/3] Enable ACPI-defined peripherals on i2c-piix4 SMBus Enrico Weigelt, metux IT consult
2019-08-09 8:33 ` Jean Delvare
2019-08-09 15:53 ` Enrico Weigelt, metux IT consult
2019-08-14 16:07 ` Wolfram Sang
2019-08-11 3:09 ` Andrew Cooks
2019-08-11 2:52 ` Andrew Cooks
2019-08-19 18:30 ` Enrico Weigelt, metux IT consult
2019-08-19 18:53 ` Wolfram Sang [this message]
2019-08-20 10:42 ` Enrico Weigelt, metux IT consult
2019-08-20 10:53 ` Wolfram Sang
2019-08-28 22:48 ` Andrew Cooks
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=20190819185334.GA9762@kunai \
--to=wsa@the-dreams.de \
--cc=acooks@rationali.st \
--cc=jdelvare@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkml@metux.net \
--cc=me@tobin.cc \
--cc=platypus-sw@opengear.com \
--cc=willw@carallon.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 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.