public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	Jean Delvare <jdelvare@suse.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/2] ACPI: Add helper acpi_use_parent_companion
Date: Thu, 26 Oct 2023 19:26:12 +0200	[thread overview]
Message-ID: <ZTqhNCNCtUk+mz1n@shikoro> (raw)
In-Reply-To: <20231024173338.haei2py7izlqxjmw@zenone.zhora.eu>

[-- Attachment #1: Type: text/plain, Size: 301 bytes --]


> Wolfram, can we take this in i2c? Otherwise this will take two
> release rounds to get in.

In general, I can, no problem. But there is still on-going discussion
regarding patch 2. So, I will wait for a conclusion there. I am not
familiar enough with ACPI to have an own opinion about that topic.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-10-26 17:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 21:33 [PATCH 0/2] Add and use new helper acpi_use_parent_companion Heiner Kallweit
2023-10-15 21:34 ` [PATCH 1/2] ACPI: Add " Heiner Kallweit
2023-10-15 21:36   ` [PATCH 2/2] i2c: i801: Use new " Heiner Kallweit
2023-10-16 16:09     ` Wilczynski, Michal
2023-10-16 17:32       ` Rafael J. Wysocki
2023-10-16 20:05         ` Heiner Kallweit
2023-10-24 13:09           ` Jean Delvare
2023-10-28 13:29             ` Wolfram Sang
2023-10-24 17:34     ` Andi Shyti
2023-10-28 13:31     ` Wolfram Sang
2023-10-18 10:51   ` [PATCH 1/2] ACPI: Add " Rafael J. Wysocki
2023-10-18 12:19     ` Heiner Kallweit
2023-10-24 17:33   ` Andi Shyti
2023-10-26 17:26     ` Wolfram Sang [this message]
2023-10-26 20:17       ` Heiner Kallweit
2023-10-28 13:30   ` Wolfram Sang

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=ZTqhNCNCtUk+mz1n@shikoro \
    --to=wsa@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=rafael@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