From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Konstantin Aladyshev <aladyshev22@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: i2c: piix4: Add ACPI section
Date: Mon, 11 Nov 2024 16:15:06 +0200 [thread overview]
Message-ID: <ZzIRakOl9VTAxc3w@smile.fi.intel.com> (raw)
In-Reply-To: <20241111140231.15198-1-aladyshev22@gmail.com>
+Cc: Andi
On Mon, Nov 11, 2024 at 05:02:31PM +0300, Konstantin Aladyshev wrote:
> Provide information how to reference I2C busses created by the PIIX4
> chip driver from the ACPI code.
So, this is not ideal, but it's a good start so far.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
We may amend this later on.
Thanks!
> Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
> ---
This place is for changelog and comments, if any. Since this is a v2 of a
standalone patch, the changelog is good to have. No need to resend now,
you can just reply to your original v2 with the missing changelog.
> Documentation/i2c/busses/i2c-piix4.rst | 62 ++++++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-11 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 11:56 [PATCH] docs: i2c: piix4: Add ACPI section Konstantin Aladyshev
2024-11-11 12:52 ` Andy Shevchenko
2024-11-11 12:53 ` Andy Shevchenko
2024-11-11 14:02 ` [PATCH v2] " Konstantin Aladyshev
2024-11-11 14:15 ` Andy Shevchenko [this message]
2024-11-11 22:35 ` Andi Shyti
2024-11-12 0:51 ` Bagas Sanjaya
2024-11-13 22:50 ` Andi Shyti
2024-11-14 8:01 ` Konstantin Aladyshev
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=ZzIRakOl9VTAxc3w@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=aladyshev22@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox