From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Rich Felker <dalias@libc.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Harry Wei <harryxiyou@gmail.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jonathan Corbet <corbet@lwn.net>,
linux-sh@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-kernel@lists.infradead.org, Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 18/39] docs: admin-guide: add kdump documentation into it
Date: Sat, 6 Jul 2019 08:46:38 -0300 [thread overview]
Message-ID: <20190706084638.7dc875f2@coco.lan> (raw)
In-Reply-To: <20190705055904.GB2790@localhost.localdomain>
Em Fri, 5 Jul 2019 13:59:04 +0800
Dave Young <dyoung@redhat.com> escreveu:
> On 07/05/19 at 11:43am, Alex Shi wrote:
> >
> >
> > 在 2019/6/28 下午8:30, Mauro Carvalho Chehab 写道:
> > > The Kdump documentation describes procedures with admins use
> > > in order to solve issues on their systems.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > Documentation/admin-guide/bug-hunting.rst | 4 ++--
> > > Documentation/admin-guide/index.rst | 1 +
> > > Documentation/{ => admin-guide}/kdump/gdbmacros.txt | 0
> > > Documentation/{ => admin-guide}/kdump/index.rst | 1 -
> > > Documentation/{ => admin-guide}/kdump/kdump.rst | 0
> > > Documentation/{ => admin-guide}/kdump/vmcoreinfo.rst | 0
> >
> > I am not sure if it's convenience for people to have more levels in docs.
> >
> > But I guess, move archs into a Documentation/arch/ dir should be fine. like Documentation/arch/{x86,arm,arm64,ia64,m68k,s390,powerpc,...}
>
> Alex, moving kdump to admin-guide sounds reasonable to me. I also agree
> with you for those arch dependent files can be moved to
> Documentation/arch/, maybe you are talking about some other patches in
> the series for the arch/?
Alex,
It makes sense for me to have a Documentation/arch directory, and place
the arch-specific docs over there.
There's actually a technical advantage on doing that: Sphinx is dumb
with regards to PDF/LaTeX output: it requires all top documents to be
listed at Documentation/conf.py, under this var:
latex_documents = [
...
]
As it creates one runtime Makefile at Documentation/output per listed
document there. So, the more we group such documents, the less merge
conflicts we'll have at Documentation/conf.py.
Btw, there's a [TECH TOPIC] proposal for KS/2019 meant to discuss
Documentation.
I suspect we could discuss the pros/cons of doing such change there.
My personal view is that we should keep the Documentation/ root dir as
clean as possible as a long term goal.
On the other hand, it makes the path bigger and harder to rename.
On a side note, last time we discussed documentation at KS I remember
I proposed to shortcut "Documentation/" to just "docs/". The consensus
on that time were to keep the big name. I still think that a shorter
one could help people to remind where documentation will be located.
Thanks,
Mauro
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Alex Shi <alex.shi@linux.alibaba.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Harry Wei <harryxiyou@gmail.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Russell King <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kexec@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 18/39] docs: admin-guide: add kdump documentation into it
Date: Sat, 6 Jul 2019 08:46:38 -0300 [thread overview]
Message-ID: <20190706084638.7dc875f2@coco.lan> (raw)
In-Reply-To: <20190705055904.GB2790@localhost.localdomain>
Em Fri, 5 Jul 2019 13:59:04 +0800
Dave Young <dyoung@redhat.com> escreveu:
> On 07/05/19 at 11:43am, Alex Shi wrote:
> >
> >
> > 在 2019/6/28 下午8:30, Mauro Carvalho Chehab 写道:
> > > The Kdump documentation describes procedures with admins use
> > > in order to solve issues on their systems.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > Documentation/admin-guide/bug-hunting.rst | 4 ++--
> > > Documentation/admin-guide/index.rst | 1 +
> > > Documentation/{ => admin-guide}/kdump/gdbmacros.txt | 0
> > > Documentation/{ => admin-guide}/kdump/index.rst | 1 -
> > > Documentation/{ => admin-guide}/kdump/kdump.rst | 0
> > > Documentation/{ => admin-guide}/kdump/vmcoreinfo.rst | 0
> >
> > I am not sure if it's convenience for people to have more levels in docs.
> >
> > But I guess, move archs into a Documentation/arch/ dir should be fine. like Documentation/arch/{x86,arm,arm64,ia64,m68k,s390,powerpc,...}
>
> Alex, moving kdump to admin-guide sounds reasonable to me. I also agree
> with you for those arch dependent files can be moved to
> Documentation/arch/, maybe you are talking about some other patches in
> the series for the arch/?
Alex,
It makes sense for me to have a Documentation/arch directory, and place
the arch-specific docs over there.
There's actually a technical advantage on doing that: Sphinx is dumb
with regards to PDF/LaTeX output: it requires all top documents to be
listed at Documentation/conf.py, under this var:
latex_documents = [
...
]
As it creates one runtime Makefile at Documentation/output per listed
document there. So, the more we group such documents, the less merge
conflicts we'll have at Documentation/conf.py.
Btw, there's a [TECH TOPIC] proposal for KS/2019 meant to discuss
Documentation.
I suspect we could discuss the pros/cons of doing such change there.
My personal view is that we should keep the Documentation/ root dir as
clean as possible as a long term goal.
On the other hand, it makes the path bigger and harder to rename.
On a side note, last time we discussed documentation at KS I remember
I proposed to shortcut "Documentation/" to just "docs/". The consensus
on that time were to keep the big name. I still think that a shorter
one could help people to remind where documentation will be located.
Thanks,
Mauro
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Rich Felker <dalias@libc.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Harry Wei <harryxiyou@gmail.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jonathan Corbet <corbet@lwn.net>,
linux-sh@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-kernel@lists.infradead.org, Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 18/39] docs: admin-guide: add kdump documentation into it
Date: Sat, 06 Jul 2019 11:46:38 +0000 [thread overview]
Message-ID: <20190706084638.7dc875f2@coco.lan> (raw)
In-Reply-To: <20190705055904.GB2790@localhost.localdomain>
Em Fri, 5 Jul 2019 13:59:04 +0800
Dave Young <dyoung@redhat.com> escreveu:
> On 07/05/19 at 11:43am, Alex Shi wrote:
> >
> >
> > 在 2019/6/28 下午8:30, Mauro Carvalho Chehab 写道:
> > > The Kdump documentation describes procedures with admins use
> > > in order to solve issues on their systems.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > Documentation/admin-guide/bug-hunting.rst | 4 ++--
> > > Documentation/admin-guide/index.rst | 1 +
> > > Documentation/{ => admin-guide}/kdump/gdbmacros.txt | 0
> > > Documentation/{ => admin-guide}/kdump/index.rst | 1 -
> > > Documentation/{ => admin-guide}/kdump/kdump.rst | 0
> > > Documentation/{ => admin-guide}/kdump/vmcoreinfo.rst | 0
> >
> > I am not sure if it's convenience for people to have more levels in docs.
> >
> > But I guess, move archs into a Documentation/arch/ dir should be fine. like Documentation/arch/{x86,arm,arm64,ia64,m68k,s390,powerpc,...}
>
> Alex, moving kdump to admin-guide sounds reasonable to me. I also agree
> with you for those arch dependent files can be moved to
> Documentation/arch/, maybe you are talking about some other patches in
> the series for the arch/?
Alex,
It makes sense for me to have a Documentation/arch directory, and place
the arch-specific docs over there.
There's actually a technical advantage on doing that: Sphinx is dumb
with regards to PDF/LaTeX output: it requires all top documents to be
listed at Documentation/conf.py, under this var:
latex_documents = [
...
]
As it creates one runtime Makefile at Documentation/output per listed
document there. So, the more we group such documents, the less merge
conflicts we'll have at Documentation/conf.py.
Btw, there's a [TECH TOPIC] proposal for KS/2019 meant to discuss
Documentation.
I suspect we could discuss the pros/cons of doing such change there.
My personal view is that we should keep the Documentation/ root dir as
clean as possible as a long term goal.
On the other hand, it makes the path bigger and harder to rename.
On a side note, last time we discussed documentation at KS I remember
I proposed to shortcut "Documentation/" to just "docs/". The consensus
on that time were to keep the big name. I still think that a shorter
one could help people to remind where documentation will be located.
Thanks,
Mauro
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Rich Felker <dalias@libc.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Harry Wei <harryxiyou@gmail.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jonathan Corbet <corbet@lwn.net>,
linux-sh@vger.kernel.org, x86@kernel.org,
Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-kernel@lists.infradead.org, Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 18/39] docs: admin-guide: add kdump documentation into it
Date: Sat, 6 Jul 2019 08:46:38 -0300 [thread overview]
Message-ID: <20190706084638.7dc875f2@coco.lan> (raw)
In-Reply-To: <20190705055904.GB2790@localhost.localdomain>
Em Fri, 5 Jul 2019 13:59:04 +0800
Dave Young <dyoung@redhat.com> escreveu:
> On 07/05/19 at 11:43am, Alex Shi wrote:
> >
> >
> > 在 2019/6/28 下午8:30, Mauro Carvalho Chehab 写道:
> > > The Kdump documentation describes procedures with admins use
> > > in order to solve issues on their systems.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > Documentation/admin-guide/bug-hunting.rst | 4 ++--
> > > Documentation/admin-guide/index.rst | 1 +
> > > Documentation/{ => admin-guide}/kdump/gdbmacros.txt | 0
> > > Documentation/{ => admin-guide}/kdump/index.rst | 1 -
> > > Documentation/{ => admin-guide}/kdump/kdump.rst | 0
> > > Documentation/{ => admin-guide}/kdump/vmcoreinfo.rst | 0
> >
> > I am not sure if it's convenience for people to have more levels in docs.
> >
> > But I guess, move archs into a Documentation/arch/ dir should be fine. like Documentation/arch/{x86,arm,arm64,ia64,m68k,s390,powerpc,...}
>
> Alex, moving kdump to admin-guide sounds reasonable to me. I also agree
> with you for those arch dependent files can be moved to
> Documentation/arch/, maybe you are talking about some other patches in
> the series for the arch/?
Alex,
It makes sense for me to have a Documentation/arch directory, and place
the arch-specific docs over there.
There's actually a technical advantage on doing that: Sphinx is dumb
with regards to PDF/LaTeX output: it requires all top documents to be
listed at Documentation/conf.py, under this var:
latex_documents = [
...
]
As it creates one runtime Makefile at Documentation/output per listed
document there. So, the more we group such documents, the less merge
conflicts we'll have at Documentation/conf.py.
Btw, there's a [TECH TOPIC] proposal for KS/2019 meant to discuss
Documentation.
I suspect we could discuss the pros/cons of doing such change there.
My personal view is that we should keep the Documentation/ root dir as
clean as possible as a long term goal.
On the other hand, it makes the path bigger and harder to rename.
On a side note, last time we discussed documentation at KS I remember
I proposed to shortcut "Documentation/" to just "docs/". The consensus
on that time were to keep the big name. I still think that a shorter
one could help people to remind where documentation will be located.
Thanks,
Mauro
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Dave Young <dyoung@redhat.com>
Cc: Rich Felker <dalias@libc.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jerry Hoemann <jerry.hoemann@hpe.com>,
Harry Wei <harryxiyou@gmail.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Alex Shi <alex.shi@linux.alibaba.com>,
Will Deacon <will@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Jonathan Corbet <corbet@lwn.net>,
linux-sh@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-kernel@lists.infradead.org, Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 18/39] docs: admin-guide: add kdump documentation into it
Date: Sat, 6 Jul 2019 08:46:38 -0300 [thread overview]
Message-ID: <20190706084638.7dc875f2@coco.lan> (raw)
In-Reply-To: <20190705055904.GB2790@localhost.localdomain>
Em Fri, 5 Jul 2019 13:59:04 +0800
Dave Young <dyoung@redhat.com> escreveu:
> On 07/05/19 at 11:43am, Alex Shi wrote:
> >
> >
> > 在 2019/6/28 下午8:30, Mauro Carvalho Chehab 写道:
> > > The Kdump documentation describes procedures with admins use
> > > in order to solve issues on their systems.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > > ---
> > > Documentation/admin-guide/bug-hunting.rst | 4 ++--
> > > Documentation/admin-guide/index.rst | 1 +
> > > Documentation/{ => admin-guide}/kdump/gdbmacros.txt | 0
> > > Documentation/{ => admin-guide}/kdump/index.rst | 1 -
> > > Documentation/{ => admin-guide}/kdump/kdump.rst | 0
> > > Documentation/{ => admin-guide}/kdump/vmcoreinfo.rst | 0
> >
> > I am not sure if it's convenience for people to have more levels in docs.
> >
> > But I guess, move archs into a Documentation/arch/ dir should be fine. like Documentation/arch/{x86,arm,arm64,ia64,m68k,s390,powerpc,...}
>
> Alex, moving kdump to admin-guide sounds reasonable to me. I also agree
> with you for those arch dependent files can be moved to
> Documentation/arch/, maybe you are talking about some other patches in
> the series for the arch/?
Alex,
It makes sense for me to have a Documentation/arch directory, and place
the arch-specific docs over there.
There's actually a technical advantage on doing that: Sphinx is dumb
with regards to PDF/LaTeX output: it requires all top documents to be
listed at Documentation/conf.py, under this var:
latex_documents = [
...
]
As it creates one runtime Makefile at Documentation/output per listed
document there. So, the more we group such documents, the less merge
conflicts we'll have at Documentation/conf.py.
Btw, there's a [TECH TOPIC] proposal for KS/2019 meant to discuss
Documentation.
I suspect we could discuss the pros/cons of doing such change there.
My personal view is that we should keep the Documentation/ root dir as
clean as possible as a long term goal.
On the other hand, it makes the path bigger and harder to rename.
On a side note, last time we discussed documentation at KS I remember
I proposed to shortcut "Documentation/" to just "docs/". The consensus
on that time were to keep the big name. I still think that a shorter
one could help people to remind where documentation will be located.
Thanks,
Mauro
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-06 11:46 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 12:29 [PATCH 00/39] Don't let ReST documents orphaned Mauro Carvalho Chehab
2019-06-28 12:29 ` [PATCH 01/39] docs: thermal: add it to the driver API Mauro Carvalho Chehab
2019-06-28 12:29 ` Mauro Carvalho Chehab
2019-06-28 12:29 ` [PATCH 02/39] docs: rapidio: " Mauro Carvalho Chehab
2019-06-28 12:29 ` [PATCH 03/39] docs: perf: move to the admin-guide Mauro Carvalho Chehab
2019-06-28 12:29 ` Mauro Carvalho Chehab
2019-06-28 12:29 ` [PATCH 04/39] docs: nvdimm: add it to the driver-api book Mauro Carvalho Chehab
2019-06-28 12:29 ` Mauro Carvalho Chehab
2019-06-28 16:33 ` Dan Williams
2019-06-28 16:33 ` Dan Williams
2019-06-28 12:29 ` [PATCH 05/39] docs: namespace: move it to the admin-guide Mauro Carvalho Chehab
2019-06-28 12:29 ` [PATCH 06/39] docs: mtd: move it to the driver-api book Mauro Carvalho Chehab
2019-06-28 12:29 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 07/39] docs: nfc: add " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 08/39] docs: mmc: move it to the driver-api Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 09/39] docs: md: move it to the driver-api book Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 10/39] docs: leds: add " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 11/39] docs: ioctl: add it to the uAPI guide Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 12/39] docs: interconnect.rst: add it to the driver-api guide Mauro Carvalho Chehab
2019-06-28 13:55 ` Georgi Djakov
2019-06-28 12:30 ` [PATCH 13/39] docs: add arch doc directories to the index Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 14/39] docs: device-mapper: move it to the admin-guide Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 15/39] docs: early-userspace: move to driver-api guide Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 16/39] docs: admin-guide: move sysctl directory to it Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 17/39] docs: admin-guide: add laptops documentation Mauro Carvalho Chehab
2019-06-28 14:51 ` Andy Shevchenko
2019-06-28 12:30 ` [PATCH 18/39] docs: admin-guide: add kdump documentation into it Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-07-05 3:43 ` Alex Shi
2019-07-05 3:43 ` Alex Shi
2019-07-05 3:43 ` Alex Shi
2019-07-05 3:43 ` Alex Shi
2019-07-05 5:59 ` Dave Young
2019-07-05 5:59 ` Dave Young
2019-07-05 5:59 ` Dave Young
2019-07-05 5:59 ` Dave Young
2019-07-05 5:59 ` Dave Young
2019-07-06 11:46 ` Mauro Carvalho Chehab [this message]
2019-07-06 11:46 ` Mauro Carvalho Chehab
2019-07-06 11:46 ` Mauro Carvalho Chehab
2019-07-06 11:46 ` Mauro Carvalho Chehab
2019-07-06 11:46 ` Mauro Carvalho Chehab
2019-07-05 5:55 ` Dave Young
2019-07-05 5:55 ` Dave Young
2019-07-05 5:55 ` Dave Young
2019-07-05 5:55 ` Dave Young
2019-07-05 5:55 ` Dave Young
2019-06-28 12:30 ` [PATCH 19/39] docs: blockdev: add it to the admin-guide Mauro Carvalho Chehab
2019-06-28 12:30 ` [Drbd-dev] " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 20/39] docs: security: move some books to it and update Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 21/39] docs: x86: move two x86-specific files to x86 arch dir Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 22/39] docs: ocxl.rst: add it to the uAPI book Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-07-01 1:21 ` Andrew Donnellan
2019-07-01 1:21 ` Andrew Donnellan
2019-06-28 12:30 ` [PATCH 23/39] docs: lp855x-driver.rst: add it to the driver-api book Mauro Carvalho Chehab
2019-06-28 12:30 ` [Intel-wired-lan] [PATCH 24/39] docs: driver-model: move " Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 18:53 ` [Intel-wired-lan] " Jeff Kirsher
2019-06-28 18:53 ` Jeff Kirsher
2019-06-28 12:30 ` [PATCH 25/39] docs: add some documentation dirs " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 26/39] docs: aoe: add it " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 27/39] docs: cgroup-v1: add it to the admin-guide book Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 28/39] docs: admin-guide: add a series of orphaned documents Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:43 ` Alexandre Belloni
2019-06-28 12:43 ` Alexandre Belloni
2019-06-28 12:43 ` Alexandre Belloni
2019-06-28 12:43 ` Alexandre Belloni
2019-06-28 12:54 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:54 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:54 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:54 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:30 ` [PATCH 29/39] docs: driver-api: " Mauro Carvalho Chehab
2019-06-28 16:38 ` Logan Gunthorpe
2019-07-02 6:19 ` Cornelia Huck
2019-06-28 12:30 ` [PATCH 30/39] docs: driver-api: add xilinx driver API documentation Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 31/39] docs: driver-api: add remaining converted dirs to it Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 32/39] docs: serial: move it to the driver-api Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 33/39] docs: phy: place documentation under driver-api Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 34/39] docs: add a memory-devices subdir to driver-api Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 35/39] docs: infiniband: add it to the driver-api bookset Mauro Carvalho Chehab
2019-07-03 18:08 ` Jason Gunthorpe
2019-07-06 11:19 ` Mauro Carvalho Chehab
2019-07-08 17:25 ` Jason Gunthorpe
2019-06-28 12:30 ` [PATCH 36/39] docs: add SPDX tags to new index files Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` [Drbd-dev] " Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 37/39] docs: adds some directories to the main documentation index Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:30 ` Mauro Carvalho Chehab
2019-06-28 12:55 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:55 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:55 ` Bartlomiej Zolnierkiewicz
2019-06-28 12:30 ` [PATCH 38/39] docs: locking: add it to the main index Mauro Carvalho Chehab
2019-06-28 12:30 ` [PATCH 39/39] docs: gpio: add sysfs interface to the admin-guide Mauro Carvalho Chehab
2019-07-03 8:44 ` Linus Walleij
2019-07-06 11:43 ` Mauro Carvalho Chehab
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=20190706084638.7dc875f2@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=alex.shi@linux.alibaba.com \
--cc=benh@kernel.crashing.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dalias@libc.org \
--cc=dyoung@redhat.com \
--cc=harryxiyou@gmail.com \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hpe.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mchehab@infradead.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.