From: "吳昊澄 Ricky" <ricky_wu@realtek.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"vaibhavgupta40@gmail.com" <vaibhavgupta40@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v4] Fixes: misc: rtsx: init value of aspm_enabled
Date: Fri, 22 Jan 2021 09:55:44 +0000 [thread overview]
Message-ID: <c55d960dd9424914b48638afcdfb81d1@realtek.com> (raw)
In-Reply-To: <YAqMkU4fR5z6aG1Z@kroah.com>
> -----Original Message-----
> From: Greg KH <gregkh@linuxfoundation.org>
> Sent: Friday, January 22, 2021 4:28 PM
> To: 吳昊澄 Ricky <ricky_wu@realtek.com>
> Cc: arnd@arndb.de; bhelgaas@google.com; vaibhavgupta40@gmail.com;
> linux-kernel@vger.kernel.org; stable@vger.kernel.org
> Subject: Re: [PATCH v4] Fixes: misc: rtsx: init value of aspm_enabled
>
> On Fri, Jan 22, 2021 at 04:19:06PM +0800, ricky_wu@realtek.com wrote:
> > From: Ricky Wu <ricky_wu@realtek.com>
> >
> > make sure ASPM state sync with pcr->aspm_enabled init value
> > pcr->aspm_enabled
> >
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Ricky Wu <ricky_wu@realtek.com>
> > ---
> >
> > v2: fixed conditions in v1 if-statement
> > v3: give description for v1 and v2
> > v4: move version change below ---
>
> What commit id does this fix? How far back should the stable backporting go?
> That's what we use the Fixes: line for.
>
I think I misunderstanding you
Fix commit id: d928061c3143de36c17650ce7b60760fefb8336c
So I need to have v5 and add "Fixes:" tag like below in the signed off by area?
"Fixes: d928061c3143de36c17650ce7b60760fefb8336c"
thanks
Ricky
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2021-01-22 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 8:19 [PATCH v4] Fixes: misc: rtsx: init value of aspm_enabled ricky_wu
2021-01-22 8:28 ` Greg KH
2021-01-22 9:55 ` 吳昊澄 Ricky [this message]
2021-01-22 10:03 ` Greg KH
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=c55d960dd9424914b48638afcdfb81d1@realtek.com \
--to=ricky_wu@realtek.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vaibhavgupta40@gmail.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