From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Changbin Du <changbin.du@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 02/57] docs: acpi: convert text files to ReST
Date: Mon, 22 Apr 2019 10:31:02 -0300 [thread overview]
Message-ID: <20190422103102.03f9548a@coco.lan> (raw)
In-Reply-To: <20190416145518.xigzqsawvbrospir@mail.google.com>
Em Tue, 16 Apr 2019 14:55:19 +0000
Changbin Du <changbin.du@gmail.com> escreveu:
> On Tue, Apr 16, 2019 at 10:17:11AM +0200, Rafael J. Wysocki wrote:
> > On Tue, Apr 16, 2019 at 5:02 AM Mauro Carvalho Chehab
> > <mchehab+samsung@kernel.org> wrote:
> > >
> > > Most of the files are already in good shape, making easier to
> > > convert them to ReST by adding proper title markups and
> > > addressing some identation and markups to properly format the
> > > document.
> >
> > There is concurrent work on this under way, please see
> > https://marc.info/?t=155381845300002&r=2&w=2
> >
> I will update the serias asap. I am just a little busy these days. My
> conversion includes pci, acpi and x86, others are not touched.
Ok, I sent a new patch series without pci, acpi and x86.
While these aren't merged upstream, I'm keeping my old patches
on my tree:
https://git.linuxtv.org/mchehab/experimental.git/commit/?h=convert_rst_v2&id=805b16dd336dd3c27733f02ec8164b2a182972a3
https://git.linuxtv.org/mchehab/experimental.git/commit/?h=convert_rst_v2&id=c950031ccb87ea14ff4c56f2433072d580db3572
https://git.linuxtv.org/mchehab/experimental.git/commit/?h=convert_rst_v2&id=4f8afce866dcd8067206b3ee493ed0b682694f49
If you find anything there that would be interesting for your
series, feel free to pick from them. Everything is based on
linux-next.
Thanks,
Mauro
next prev parent reply other threads:[~2019-04-22 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 2:55 [PATCH 00/57] Convert files to ReST Mauro Carvalho Chehab
2019-04-16 2:55 ` Mauro Carvalho Chehab
2019-04-16 2:55 ` [PATCH 02/57] docs: acpi: convert text " Mauro Carvalho Chehab
2019-04-16 2:55 ` Mauro Carvalho Chehab
2019-04-16 8:17 ` Rafael J. Wysocki
2019-04-16 8:17 ` Rafael J. Wysocki
2019-04-16 9:54 ` Mauro Carvalho Chehab
2019-04-16 9:54 ` Mauro Carvalho Chehab
2019-04-16 10:17 ` Rafael J. Wysocki
2019-04-16 10:17 ` Rafael J. Wysocki
2019-04-16 14:55 ` Changbin Du
2019-04-16 14:55 ` Changbin Du
2019-04-22 13:31 ` Mauro Carvalho Chehab [this message]
2019-04-22 13:31 ` Mauro Carvalho Chehab
2019-04-16 2:55 ` [PATCH 11/57] docs: extcon: move it to acpi dir and convert it " Mauro Carvalho Chehab
2019-04-16 2:55 ` Mauro Carvalho Chehab
2019-04-18 12:42 ` Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files " Mauro Carvalho Chehab
2019-04-18 12:42 ` Mauro Carvalho Chehab
2019-04-19 22:10 ` Jonathan Corbet
2019-04-19 22:10 ` Jonathan Corbet
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=20190422103102.03f9548a@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=changbin.du@gmail.com \
--cc=corbet@lwn.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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