From: Andi Shyti <andi.shyti@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [RESEND PATCH] drm/i915: constify pointers to hwmon_channel_info
Date: Fri, 19 May 2023 01:54:00 +0200 [thread overview]
Message-ID: <ZGa6mAe726ER7N4t@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230511175446.282041-1-krzysztof.kozlowski@linaro.org>
Hi Krzysztof,
On Thu, May 11, 2023 at 07:54:46PM +0200, Krzysztof Kozlowski wrote:
> Statically allocated array of pointers to hwmon_channel_info can be made
> const for safety.
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2023-05-18 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 17:54 [Intel-gfx] [RESEND PATCH] drm/i915: constify pointers to hwmon_channel_info Krzysztof Kozlowski
2023-05-15 21:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-05-16 10:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: constify pointers to hwmon_channel_info (rev2) Patchwork
2023-05-16 14:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-17 9:28 ` [Intel-gfx] [RESEND PATCH] drm/i915: constify pointers to hwmon_channel_info Jani Nikula
[not found] ` <2a1b81da-39c8-4111-7e42-18f5f2f557c4@linaro.org>
2023-05-17 9:38 ` Jani Nikula
2023-05-23 9:49 ` Jani Nikula
2023-05-18 23:54 ` Andi Shyti [this message]
2023-05-25 9:22 ` Jani Nikula
2023-08-18 11:03 ` Jani Nikula
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=ZGa6mAe726ER7N4t@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.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