From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jean Delvare <jdelvare@suse.de>, Hector Martin <marcan@marcan.st>
Cc: Alex Henrie <alexh@vpitech.com>, Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
Ettore Chimenti <ek5.chimenti@gmail.com>
Subject: Re: [PATCH v3] i2c: i801: Safely share SMBus with BIOS/ACPI
Date: Thu, 15 Dec 2022 22:09:51 +0100 [thread overview]
Message-ID: <43cc28d2-2dce-730a-0d23-251b1c3b8713@gmail.com> (raw)
In-Reply-To: <20221215152641.39164ca3@endymion.delvare>
On 15.12.2022 15:26, Jean Delvare wrote:
> Hi all,
>
> I know it's been a while, and I have to apologize for that. The
> original plan was to merge the patch series from Heiner Kallweit first,
> but as it turns out, it was never resubmitted after my (admittedly
> slow) review and things got stuck.
>
Indeed, this has been stuck. I have to set finishing this series on
my task list again.
> Anyway, I finally took some time to review this patch. I have a good
> headache now, and some comments below.
>
[...]
next prev parent reply other threads:[~2022-12-15 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 5:41 [PATCH v3] i2c: i801: Safely share SMBus with BIOS/ACPI Hector Martin
2021-11-29 9:00 ` Wolfram Sang
2021-11-30 9:26 ` Jean Delvare
2022-01-19 20:48 ` Alex Henrie
2022-01-24 18:22 ` Alex Henrie
2022-07-20 19:21 ` Ettore Chimenti
2022-12-15 14:26 ` Jean Delvare
2022-12-15 21:09 ` Heiner Kallweit [this message]
2022-12-17 13:28 ` Hector Martin
2022-12-18 23:02 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 0:31 Alex Henrie
2021-12-17 7:41 ` Hector Martin
2021-12-18 2:51 ` [External] " Alex Henrie
2021-12-18 3:39 ` Hector Martin
2021-12-20 17:41 ` Alex Henrie
2022-01-05 1:37 ` Alex Henrie
2022-01-08 3:47 ` Hector Martin
2022-12-13 15:10 David Oberhollenzer
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=43cc28d2-2dce-730a-0d23-251b1c3b8713@gmail.com \
--to=hkallweit1@gmail.com \
--cc=alexh@vpitech.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=ek5.chimenti@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--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).