From: Jani Nikula <jani.nikula@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [RESEND PATCH] drm/i915: constify pointers to hwmon_channel_info
Date: Tue, 23 May 2023 12:49:57 +0300 [thread overview]
Message-ID: <87a5xvml6i.fsf@intel.com> (raw)
In-Reply-To: <87a5y3guvv.fsf@intel.com>
On Wed, 17 May 2023, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 17 May 2023, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>> On 17/05/2023 11:28, Jani Nikula wrote:
>>> On Thu, 11 May 2023, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 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>
>>>
>>> FYI we'll merge this once we've done a backmerge to get the hwmon
>>> changes to our tree.
>>
>> There are no dependencies. hwmon changes are already in rc1.
>
> That's what I'm saying, drm-intel-next doesn't have rc1. :)
Pushed to drm-intel-next, thanks for the patch.
BR,
Jani.
>
> BR,
> Jani.
>
>>
>> Best regards,
>> Krzysztof
>>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] drm/i915: constify pointers to hwmon_channel_info
Date: Tue, 23 May 2023 12:49:57 +0300 [thread overview]
Message-ID: <87a5xvml6i.fsf@intel.com> (raw)
In-Reply-To: <87a5y3guvv.fsf@intel.com>
On Wed, 17 May 2023, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 17 May 2023, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>> On 17/05/2023 11:28, Jani Nikula wrote:
>>> On Thu, 11 May 2023, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> 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>
>>>
>>> FYI we'll merge this once we've done a backmerge to get the hwmon
>>> changes to our tree.
>>
>> There are no dependencies. hwmon changes are already in rc1.
>
> That's what I'm saying, drm-intel-next doesn't have rc1. :)
Pushed to drm-intel-next, thanks for the patch.
BR,
Jani.
>
> BR,
> Jani.
>
>>
>> Best regards,
>> Krzysztof
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-23 9:50 UTC|newest]
Thread overview: 19+ 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-11 17:54 ` Krzysztof Kozlowski
2023-05-11 17:54 ` 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
2023-05-17 9:28 ` Jani Nikula
2023-05-17 9:30 ` Krzysztof Kozlowski
2023-05-17 9:38 ` [Intel-gfx] " Jani Nikula
2023-05-17 9:38 ` Jani Nikula
2023-05-23 9:49 ` Jani Nikula [this message]
2023-05-23 9:49 ` Jani Nikula
2023-05-18 23:54 ` [Intel-gfx] " Andi Shyti
2023-05-18 23:54 ` Andi Shyti
2023-05-18 23:54 ` Andi Shyti
2023-05-25 9:22 ` Jani Nikula
2023-05-25 9:22 ` Jani Nikula
2023-08-18 11:03 ` [Intel-gfx] " 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=87a5xvml6i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.