public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: <wen.yang99@zte•com.cn>
To: <chzigotzky@xenosoft•de>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re:[PATCH v3] cpufreq/pasemi: fix an use-after-free inpas_cpufreq_cpu_init()
Date: Tue, 9 Jul 2019 09:39:16 +0800 (CST)	[thread overview]
Message-ID: <201907090939164296374@zte.com.cn> (raw)
In-Reply-To: <3c1d01ef-5d2a-2ec6-aeeb-b7936515a119@xenosoft.de>


[-- Attachment #1.1: Type: text/plain, Size: 279 bytes --]

> Hello Wen,
> 
> Thanks for your patch!
> 
> Did you test your patch with a P.A. Semi board?
> 

Hello Christian, thank you.
We don't have a P.A. Semi board yet, so we didn't test it.
If you have such a board, could you please kindly help to test it?

--
Thanks and regards,
Wen

  reply	other threads:[~2019-07-09  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 21:01 [PATCH v3] cpufreq/pasemi: fix an use-after-free in pas_cpufreq_cpu_init() Christian Zigotzky
2019-07-09  1:39 ` wen.yang99 [this message]
2019-07-10  7:55   ` [PATCH v3] cpufreq/pasemi: fix an use-after-free inpas_cpufreq_cpu_init() Christian Zigotzky
2019-07-18 12:46   ` [PATCH v7] " Christian Zigotzky
2019-07-19  5:53     ` Re:[PATCH v7] cpufreq/pasemi: fix an use-after-freeinpas_cpufreq_cpu_init() wen.yang99

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=201907090939164296374@zte.com.cn \
    --to=wen.yang99@zte$(echo .)com.cn \
    --cc=chzigotzky@xenosoft$(echo .)de \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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