From: Alex Shi <seakeel@gmail.com>
To: Yanteng Si <siyanteng@loongson.cn>, alexs@kernel.org, bobwxc@email.cn
Cc: corbet@lwn.net, chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, siyanteng01@gmail.com,
zhoubinbin@loongson.cn, yizhou.tang@shopee.com,
wanjiabing@vivo.com, leoyang.li@nxp.com, src.res@email.cn
Subject: Re: [PATCH 6/8] Docs/zh_CN: Update the translation of pci-iov-howto to 5.19-rc8
Date: Wed, 27 Jul 2022 10:19:04 +0800 [thread overview]
Message-ID: <dc6719f9-e41b-8a4e-7cfa-fe9c6f53537b@gmail.com> (raw)
In-Reply-To: <e235ea1d60809647971b5d3e89aa44e30d212336.1658740151.git.siyanteng@loongson.cn>
Reviewed-by: Alex Shi <alexs@kernel.org>
On 7/25/22 17:24, Yanteng Si wrote:
> Update to commit 4f23bd5d09af ("PCI/doc: Convert
> examples to generic power management")
>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> ---
> Documentation/translations/zh_CN/PCI/pci-iov-howto.rst | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/PCI/pci-iov-howto.rst b/Documentation/translations/zh_CN/PCI/pci-iov-howto.rst
> index fbc83dfdcead..fb023ea1374d 100644
> --- a/Documentation/translations/zh_CN/PCI/pci-iov-howto.rst
> +++ b/Documentation/translations/zh_CN/PCI/pci-iov-howto.rst
> @@ -123,14 +123,14 @@ nr_virtfn'是要启用的VF的编号。
> ...
> }
>
> - static int dev_suspend(struct pci_dev *dev, pm_message_t state)
> + static int dev_suspend(struct device *dev)
> {
> ...
>
> return 0;
> }
>
> - static int dev_resume(struct pci_dev *dev)
> + static int dev_resume(struct device *dev)
> {
> ...
>
> @@ -163,8 +163,7 @@ nr_virtfn'是要启用的VF的编号。
> .id_table = dev_id_table,
> .probe = dev_probe,
> .remove = dev_remove,
> - .suspend = dev_suspend,
> - .resume = dev_resume,
> + .driver.pm = &dev_pm_ops
> .shutdown = dev_shutdown,
> .sriov_configure = dev_sriov_configure,
> };
next prev parent reply other threads:[~2022-07-27 2:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 9:20 [PATCH 0/8] Docs/zh_CN: Update some translation to 5.19-rc8 Yanteng Si
2022-07-25 9:20 ` [PATCH 1/8] Docs/zh_CN: Update the translation of iio_configfs " Yanteng Si
2022-07-26 5:51 ` Alex Shi
2022-07-25 9:20 ` [PATCH 2/8] Docs/zh_CN: Update the translation of kasan " Yanteng Si
2022-07-27 2:15 ` Alex Shi
2022-07-28 1:17 ` YanTeng Si
2022-07-25 9:20 ` [PATCH 3/8] Docs/zh_CN: Update the translation of sparse " Yanteng Si
2022-07-27 2:16 ` Alex Shi
2022-07-25 9:23 ` [PATCH 4/8] Docs/zh_CN: Update the translation of testing-overview " Yanteng Si
2022-07-27 2:18 ` Alex Shi
2022-07-25 9:24 ` [PATCH 5/8] Docs/zh_CN: Update the translation of usage " Yanteng Si
2022-07-27 2:18 ` Alex Shi
2022-07-25 9:24 ` [PATCH 6/8] Docs/zh_CN: Update the translation of pci-iov-howto " Yanteng Si
2022-07-27 2:19 ` Alex Shi [this message]
2022-07-25 9:24 ` [PATCH 7/8] Docs/zh_CN: Update the translation of pci " Yanteng Si
2022-07-26 16:19 ` Wu XiangCheng
2022-07-27 2:20 ` Alex Shi
2022-07-25 9:24 ` [PATCH 8/8] Docs/zh_CN: Update the translation of sched-stats " Yanteng Si
2022-07-26 15:06 ` Wu XiangCheng
2022-07-27 2:20 ` Alex Shi
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=dc6719f9-e41b-8a4e-7cfa-fe9c6f53537b@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=jiaxun.yang@flygoat.com \
--cc=leoyang.li@nxp.com \
--cc=linux-doc@vger.kernel.org \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=src.res@email.cn \
--cc=wanjiabing@vivo.com \
--cc=yizhou.tang@shopee.com \
--cc=zhoubinbin@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).