mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, rafael@kernel.org
Cc: daniel.lezcano@linaro.org, amitk@kernel.org,
	srinivas.pandruvada@linux.intel.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] thermal: int340x: Misc acpi_buffer handling updates
Date: Fri, 25 Mar 2022 10:15:34 +0800	[thread overview]
Message-ID: <1c5b8eb88d8c59949a6bbd3e763c820db462979f.camel@intel.com> (raw)
In-Reply-To: <20220324190950.70486-1-dave@stgolabs.net>

Acked-by: Zhang Rui <rui.zhang@intel.com>

for the whole patch series.

thanks,
rui

On Thu, 2022-03-24 at 12:09 -0700, Davidlohr Bueso wrote:
> Hello,
> 
> The following is a fallout of eyeballing _OSC handling in the driver.
> These changes have only been compile-tested. Patch 1 is a fix and the
> other two are cleanups.
> 
> Thanks!
> 
> Davidlohr Bueso (3):
>   thermal: int340x: Fix bogus acpi_buffer pointer freeing
>   thermal: int340x: Consolidate freeing of acpi_buffer pointer
>   thermal: int340x: Cleanup osc context init
> 
>  .../intel/int340x_thermal/int3400_thermal.c   | 24 +++++++--------
> ----
>  1 file changed, 9 insertions(+), 15 deletions(-)
> 
> --
> 2.26.2
> 


      parent reply	other threads:[~2022-03-25  2:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 19:09 Davidlohr Bueso
2022-03-24 19:09 ` [PATCH 1/3] thermal: int340x: Fix bogus acpi_buffer pointer freeing Davidlohr Bueso
2022-03-25 12:25   ` srinivas pandruvada
2022-04-05 18:27   ` Rafael J. Wysocki
2022-03-24 19:09 ` [PATCH 2/3] thermal: int340x: Consolidate freeing of acpi_buffer pointer Davidlohr Bueso
2022-03-24 19:09 ` [PATCH 3/3] thermal: int340x: Cleanup osc context init Davidlohr Bueso
2022-03-25  2:15 ` Zhang Rui [this message]

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=1c5b8eb88d8c59949a6bbd3e763c820db462979f.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=srinivas.pandruvada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®