From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org,
'Linux Kernel' <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org, Dell.Client.Kernel@dell.com,
linux-iio@vger.kernel.org,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Huang Jianan <huangjianan@oppo.com>, Chao Yu <chao@kernel.org>,
Divya Bharathi <divya.bharathi@dell.com>,
Mark Pearson <markpearson@lenovo.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Gwendal Grignou <gwendal@chromium.org>,
Kajol Jain <kjain@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
"David E. Box" <david.e.box@linux.intel.com>,
Mark Gross <markgross@kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: unexpected indentation warning in Documentation/ABI/testing/sysfs-*
Date: Mon, 4 Apr 2022 19:26:33 +0700 [thread overview]
Message-ID: <abc7cc7d-b21c-7b6e-487d-f8f8896b40e7@gmail.com> (raw)
In-Reply-To: <YkreSbV4+KmW1/zV@kroah.com>
On 04/04/22 19.02, Greg Kroah-Hartman wrote:
>> Presumably because Sphinx mistakes these documentation files without
>> extensions for .rst files? I dunno.
>>
>> Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
>
> Care to send patches to fix these up?
>
> thanks,
>
> greg k-h
Hi Greg,
I'm sorry I couldn't do any fixes for now. I'm just reporting.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-04 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 11:58 unexpected indentation warning in Documentation/ABI/testing/sysfs-* Bagas Sanjaya
2022-04-04 12:02 ` Greg Kroah-Hartman
2022-04-04 12:26 ` Bagas Sanjaya [this message]
2022-04-04 12:54 ` Hans de Goede
2022-04-05 7:52 ` Bagas Sanjaya
2022-04-05 9:32 ` Gao Xiang
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=abc7cc7d-b21c-7b6e-487d-f8f8896b40e7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=akpm@linux-foundation.org \
--cc=chao@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david.e.box@linux.intel.com \
--cc=divya.bharathi@dell.com \
--cc=gregkh@linuxfoundation.org \
--cc=gwendal@chromium.org \
--cc=hdegoede@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huangjianan@oppo.com \
--cc=jic23@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=markpearson@lenovo.com \
--cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox