From: Peter Rosin <peda@axentia.se>
To: Wolfram Sang <wsa@kernel.org>, Evan Green <evgreen@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land
Date: Fri, 15 Jan 2021 10:29:46 +0100 [thread overview]
Message-ID: <6fd88320-740e-2fd6-8823-500032d0e541@axentia.se> (raw)
In-Reply-To: <20210114195330.GA16693@kunai>
On 2021-01-14 20:53, Wolfram Sang wrote:
>> Can this be accepted as-is, or should I resend?
>
> Peter, can you have a look here as well?
I have no issues, but I was waiting for a response from Andy here. I have
little knowledge of ACPI, and have previously made ignorant mistakes in
that area. I would greatly appreciate Andy following through with his
line of thinking...
So, if we ignore Andys review comments, then:
Acked-by: Peter Rosin <peda@axentia.se>
Cheers,
Peter
next prev parent reply other threads:[~2021-01-15 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 23:40 [RESEND PATCH v3 0/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land Evan Green
2020-11-18 23:40 ` [RESEND PATCH v3 1/2] i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt() Evan Green
2021-01-15 9:30 ` Peter Rosin
2021-01-17 11:53 ` Wolfram Sang
2020-11-18 23:40 ` [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land Evan Green
2020-11-19 15:25 ` Andy Shevchenko
2020-11-20 18:59 ` Evan Green
2020-11-30 19:11 ` Evan Green
2020-12-09 23:03 ` Evan Green
2021-01-05 10:25 ` Wolfram Sang
2021-01-14 18:17 ` Evan Green
2021-01-14 19:53 ` Wolfram Sang
2021-01-15 9:29 ` Peter Rosin [this message]
2021-01-19 12:10 ` Andy Shevchenko
2021-01-17 11:54 ` Wolfram Sang
2021-01-17 17:15 ` Evan Green
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=6fd88320-740e-2fd6-8823-500032d0e541@axentia.se \
--to=peda@axentia.se \
--cc=andriy.shevchenko@linux.intel.com \
--cc=evgreen@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=rdunlap@infradead.org \
--cc=wsa@kernel.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).