From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: Huang Rui <ray.huang-5C7GfCeVMHo@public.gmane.org>,
Greg KH
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: "Deucher,
Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>,
"Wang, Ken" <Ken.Wang-5C7GfCeVMHo@public.gmane.org>,
"stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] drm/amdgpu: read reg in each iterate of psp_wait_for loop
Date: Tue, 18 Jul 2017 10:50:27 +0800 [thread overview]
Message-ID: <596D7773.3010602@amd.com> (raw)
In-Reply-To: <20170717114511.GA18478@hr-amur2>
On 07/17/2017 07:45 PM, Huang Rui wrote:
> On Mon, Jul 17, 2017 at 06:57:41PM +0800, Greg KH wrote:
>> On Mon, Jul 17, 2017 at 04:56:26PM +0800, Zhang, Jerry (Junwei) wrote:
>> > + stable@vger.kernel.org
>>
>> <formletter>
>>
>> This is not the correct way to submit patches for inclusion in the
>> stable kernel tree. Please read:
>>https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>> for how to do this properly.
>>
>> </formletter>
>
> Thanks, Greg. :-)
Thanks Greg to reminder that
>
>>> BTW: please add Cc: <stable@vger.kernel.org> in your patch, it need be
>>> backported to stable tree.
>
> Jerry, I might not describe it clearly. We need follow the rule that Greg
> provided. Actually, I meant to add Cc in your commit message like below,
> then sent it out:
Thanks to explain in detail.
I will prepare it them as one patch again.
Jerry
>
> 8<----------
>
> Subject: [PATCH] drm/amdgpu: read reg in each iterate of psp_wait_for loop
>
> This fixes the SOS loading failure of psp v3.1.
>
> Signed-off-by: Junwei Zhang <Jerry.Zhang@amd.com>
> Cc: stable@vger.kernel.org
>
> 8<----------
>
> And you'd better squeeze the two patches as one (actually it's only one
> fix) to make backporting more smooth.
>
> Thanks,
> Rui
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Zhang, Jerry (Junwei)" <Jerry.Zhang@amd.com>
To: Huang Rui <ray.huang@amd.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: "Wang, Ken" <Ken.Wang@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>
Subject: Re: [PATCH] drm/amdgpu: read reg in each iterate of psp_wait_for loop
Date: Tue, 18 Jul 2017 10:50:27 +0800 [thread overview]
Message-ID: <596D7773.3010602@amd.com> (raw)
In-Reply-To: <20170717114511.GA18478@hr-amur2>
On 07/17/2017 07:45 PM, Huang Rui wrote:
> On Mon, Jul 17, 2017 at 06:57:41PM +0800, Greg KH wrote:
>> On Mon, Jul 17, 2017 at 04:56:26PM +0800, Zhang, Jerry (Junwei) wrote:
>> > + stable@vger.kernel.org
>>
>> <formletter>
>>
>> This is not the correct way to submit patches for inclusion in the
>> stable kernel tree. Please read:
>>https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>> for how to do this properly.
>>
>> </formletter>
>
> Thanks, Greg. :-)
Thanks Greg to reminder that
>
>>> BTW: please add Cc: <stable@vger.kernel.org> in your patch, it need be
>>> backported to stable tree.
>
> Jerry, I might not describe it clearly. We need follow the rule that Greg
> provided. Actually, I meant to add Cc in your commit message like below,
> then sent it out:
Thanks to explain in detail.
I will prepare it them as one patch again.
Jerry
>
> 8<----------
>
> Subject: [PATCH] drm/amdgpu: read reg in each iterate of psp_wait_for loop
>
> This fixes the SOS loading failure of psp v3.1.
>
> Signed-off-by: Junwei Zhang <Jerry.Zhang@amd.com>
> Cc: stable@vger.kernel.org
>
> 8<----------
>
> And you'd better squeeze the two patches as one (actually it's only one
> fix) to make backporting more smooth.
>
> Thanks,
> Rui
next prev parent reply other threads:[~2017-07-18 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 10:20 [PATCH] drm/amdgpu: read reg in each iterate of psp_wait_for loop Junwei Zhang
[not found] ` <1500027617-18557-1-git-send-email-Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
2017-07-14 14:40 ` Deucher, Alexander
2017-07-17 7:52 ` Huang Rui
2017-07-17 7:57 ` Huang Rui
2017-07-17 8:56 ` Zhang, Jerry (Junwei)
2017-07-17 8:56 ` Zhang, Jerry (Junwei)
2017-07-17 10:57 ` Greg KH
[not found] ` <20170717105741.GC32372-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-07-17 11:45 ` Huang Rui
2017-07-17 11:45 ` Huang Rui
2017-07-18 2:50 ` Zhang, Jerry (Junwei) [this message]
2017-07-18 2:50 ` Zhang, Jerry (Junwei)
-- strict thread matches above, loose matches on Subject: below --
2017-07-18 2:54 Junwei Zhang
2017-07-18 2:54 ` Junwei Zhang
2017-07-18 3:25 ` Deucher, Alexander
2017-07-18 3:25 ` Deucher, Alexander
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=596D7773.3010602@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=Ken.Wang-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=ray.huang-5C7GfCeVMHo@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.