From: Wolfram Sang <wsa@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andi Shyti <andi.shyti@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v2 2/4] i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros
Date: Fri, 29 Sep 2023 09:33:47 +0200 [thread overview]
Message-ID: <ZRZ92ybPW7ZDQzjK@ninjato> (raw)
In-Reply-To: <20230927-pcc_defines-v2-2-0b8ffeaef2e5@arm.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
On Wed, Sep 27, 2023 at 05:26:11PM +0100, Sudeep Holla wrote:
> Use the newly defined common and generic PCC shared memory region
> related macros in this driver to replace the locally defined ones.
>
> Reviewed-by: Andi Shyti <andi.shyti@kernel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Acked-by: Wolfram Sang <wsa@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-29 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 16:26 [PATCH v2 0/4] ACPI: PCC: Define and use the common PCC shared memory regions related macros Sudeep Holla
2023-09-27 16:26 ` [PATCH v2 1/4] ACPI: PCC: Add PCC shared memory region command and status bitfields Sudeep Holla
2023-10-03 13:29 ` Rafael J. Wysocki
2023-10-03 14:29 ` Sudeep Holla
2023-10-03 15:05 ` Rafael J. Wysocki
2023-09-27 16:26 ` [PATCH v2 2/4] i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros Sudeep Holla
2023-09-29 7:33 ` Wolfram Sang [this message]
2023-09-27 16:26 ` [PATCH v2 3/4] hwmon: (xgene) " Sudeep Holla
2023-09-27 16:26 ` [PATCH v2 4/4] soc: kunpeng_hccs: " Sudeep Holla
2023-09-28 11:30 ` lihuisong (C)
2023-09-29 11:45 ` [PATCH v2 0/4] ACPI: PCC: Define and use the common PCC shared memory regions " Sudeep Holla
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=ZRZ92ybPW7ZDQzjK@ninjato \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=lihuisong@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rafael.j.wysocki@intel.com \
--cc=sudeep.holla@arm.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