From: Doug Anderson <dianders@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Maxime Ripard <mripard@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [linux-next:master 5684/6443] htmldocs: Documentation/gpu/todo.rst:469: WARNING: Unexpected indentation.
Date: Wed, 2 Aug 2023 07:51:31 -0700 [thread overview]
Message-ID: <CAD=FV=Vj5t2tPUX31rn1EjZcH10UGHN+AUov7N9xy6R7_VZWMQ@mail.gmail.com> (raw)
In-Reply-To: <202308022221.APCRi7vk-lkp@intel.com>
Hi,
On Wed, Aug 2, 2023 at 7:43 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 626c67169f9972fffcdf3bc3864de421f162ebf5
> commit: d2aacaf07395bd798373cbec6af05fff4147aff3 [5684/6443] drm/panel: Check for already prepared/enabled in drm_panel
> reproduce: (https://download.01.org/0day-ci/archive/20230802/202308022221.APCRi7vk-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202308022221.APCRi7vk-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> Documentation/gpu/todo.rst:469: WARNING: Unexpected indentation.
>
> vim +469 Documentation/gpu/todo.rst
>
> 465
> 466 In a whole pile of panel drivers, we have code to make the
> 467 prepare/unprepare/enable/disable callbacks behave as no-ops if they've already
> 468 been called. To get some idea of the duplicated code, try:
> > 469 git grep 'if.*>prepared' -- drivers/gpu/drm/panel
> 470 git grep 'if.*>enabled' -- drivers/gpu/drm/panel
> 471
Thanks for the report. This was reported by Stephen Rothwell a few
hours ago. I just posted a patch to fix it.
https://lore.kernel.org/all/20230802074727.2.Iaeb7b0f7951aee6b8c090364bbc87b1ae198a857@changeid/
-Doug
prev parent reply other threads:[~2023-08-02 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 14:42 kernel test robot
2023-08-02 14:51 ` Doug Anderson [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='CAD=FV=Vj5t2tPUX31rn1EjZcH10UGHN+AUov7N9xy6R7_VZWMQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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