From: Philip Li <philip.li@intel.com>
To: "Wang, Chao-kai (Stylon)" <Stylon.Wang@amd.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Shih, Jude" <Jude.Shih@amd.com>, Yann Dirson <ydirson@free.fr>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] amdgpu: fix some kernel-doc markup
Date: Tue, 23 May 2023 14:03:27 +0800 [thread overview]
Message-ID: <ZGxXL00oWbEQyIXP@rli9-mobl> (raw)
In-Reply-To: <BN9PR12MB5145A7D7D53F2572A546039DFF409@BN9PR12MB5145.namprd12.prod.outlook.com>
On Tue, May 23, 2023 at 05:02:02AM +0000, Wang, Chao-kai (Stylon) wrote:
> [AMD Official Use Only - General]
>
> Hi Greg,
>
> To be honest, this is just to fix a build error/warning from a Linux kernel performance test:
> https://lore.kernel.org/oe-kbuild-all/202302281017.9qcgLAZi-lkp@intel.com/
Sorry about the confusing report. We will stop the documentation test on linux-stable.git.
>
> No real bug/fix involved.
>
>
> Regards
>
> Stylon Wang
>
> MTS Software Development Eng. | AMD
> Display Solution Team
>
> O +(886) 2-3789-3667 ext. 23667 C +(886) 921-897-142
>
> ----------------------------------------------------------------------------------------------------------------------------------
>
> 6F, 3, YuanCyu St (NanKang Software Park) Taipei, Taiwan
>
> Facebook<https://www.facebook.com/AMD> | Twitter<https://twitter.com/AMD> | amd.com<http://www.amd.com/>
>
>
>
> ________________________________
> From: Greg KH <gregkh@linuxfoundation.org>
> Sent: May 23, 2023 2:41 AM
> To: Wang, Chao-kai (Stylon) <Stylon.Wang@amd.com>
> Cc: stable@vger.kernel.org <stable@vger.kernel.org>; Shih, Jude <Jude.Shih@amd.com>; Yann Dirson <ydirson@free.fr>; Deucher, Alexander <Alexander.Deucher@amd.com>; kernel test robot <lkp@intel.com>
> Subject: Re: [PATCH] amdgpu: fix some kernel-doc markup
>
> On Mon, May 22, 2023 at 08:04:13PM +0800, Stylon Wang wrote:
> > From: Yann Dirson <ydirson@free.fr>
> >
> > commit 03f2abb07e54b3e0da54c52a656d9765b7e141c5 upstream.
> >
> > Those are not today pulled by the sphinx doc, but better be ready.
> >
> > Two lines of the cherry-picked patch is removed because they are being
> > refactored away from this file:
> > drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
> >
> > Signed-off-by: Yann Dirson <ydirson@free.fr>
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Link: https://lore.kernel.org/oe-kbuild-all/202302281017.9qcgLAZi-lkp@intel.com/
> > Cc: <stable@vger.kernel.org> # 5.15.x
> > (cherry picked from commit 03f2abb07e54b3e0da54c52a656d9765b7e141c5)
>
> why is kernel doc issues stable material? What real fix needs this?
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2023-05-23 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 12:04 [PATCH] amdgpu: fix some kernel-doc markup Stylon Wang
2023-05-22 18:41 ` Greg KH
[not found] ` <BN9PR12MB5145A7D7D53F2572A546039DFF409@BN9PR12MB5145.namprd12.prod.outlook.com>
2023-05-23 6:03 ` Philip Li [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=ZGxXL00oWbEQyIXP@rli9-mobl \
--to=philip.li@intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Jude.Shih@amd.com \
--cc=Stylon.Wang@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=lkp@intel.com \
--cc=stable@vger.kernel.org \
--cc=ydirson@free.fr \
/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