From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-ide@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-ia64@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Richard Sailer <richard@weltraumpflege.org>,
"Herton R. Krzesinski" <herton@redhat.com>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Jaroslav Kysela <perex@perex.cz>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Jiri Slaby <jslaby@suse.cz>, Ingo Molnar <mingo@kernel.org>,
Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>,
Markus Heiser <markus.heiser@darmarit.de>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>Sanjeev <g>
Subject: Re: [PATCH 00/13] Get rid of DocBook
Date: Sun, 14 May 2017 19:00:57 -0300 [thread overview]
Message-ID: <20170514190057.17e41167@vento.lan> (raw)
In-Reply-To: <CAGXu5j+KgtD+Vj8-K-3XVKdQnWQ8JJUWSjWwrhxP+ApAyyEPKg@mail.gmail.com>
Em Sun, 14 May 2017 14:05:09 -0700
Kees Cook <keescook@chromium.org> escreveu:
> On Sun, May 14, 2017 at 8:38 AM, Mauro Carvalho Chehab
> <mchehab@s-opensource.com> wrote:
> > As just one book (lsm) was missing conversion, let's convert it
> > and store as if it were a plain text file under Documentation/lsm.txt,
> > adding a notice that it requires update.
>
> I could probably fold this change into my rst-ification of
> Documentation/security/
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/rst
>
> Specifically, the new Documentation/security/LSM.rst was rather short.
> I think your lsm.txt and this one could be likely merged.
Yeah, makes sense. I'm not sure what would be the best way to
proceed, as, currently, after removing lsm.tmpl, my patch
series remove DocBook, as everything else was already removed.
I see a few ways for us to proceed:
1) You could submit the patches you have so far to docs -next,
to be merged before my patch series;
2) I could send you a patch based on your tree. I'll need to
rebase this series to be applied on the top of your tree + docs-next,
with would require that your patch series would be merged before,
at docs -next;
3) we can handle both series independently. When both gets
merged at docs -next, a simple patch, either written by you or
me, could merge both files.
IMO, (3) is simpler, but if you prefer, we can do on some other
way.
Thanks,
Mauro
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-05-14 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 15:38 [PATCH 00/13] Get rid of DocBook Mauro Carvalho Chehab
2017-05-14 15:38 ` [PATCH 05/13] ata: update references for libata documentation Mauro Carvalho Chehab
2017-05-14 21:05 ` [PATCH 00/13] Get rid of DocBook Kees Cook
2017-05-14 22:00 ` Mauro Carvalho Chehab [this message]
2017-05-15 14:34 ` Kees Cook
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=20170514190057.17e41167@vento.lan \
--to=mchehab@s-opensource.com \
--cc=alsa-devel@alsa-project.org \
--cc=corbet@lwn.net \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=egtvedt@samfundet.no \
--cc=herton@redhat.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mingo@kernel.org \
--cc=perex@perex.cz \
--cc=peterz@infradead.org \
--cc=richard@weltraumpflege.org \
--cc=yamada.masahiro@socionext.com \
/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