Re: [PATCH] docs: move powerpc under arch

Michael Ellerman writes: > On October 4, 2023 3:05:48 AM GMT+11:00, Jonathan Corbet > wrote: >>Costa Shulyupin writes: >> >>> and fix all in-tree references. >>> >>> Architecture-specific documentation is being moved into Documentation/ar

Re: [PATCH] docs: move powerpc under arch

Costa Shulyupin writes: > and fix all in-tree references. > > Architecture-specific documentation is being moved into Documentation/arch/ > as a way of cleaning up the top-level documentation directory and making > the docs hierarchy more closely match the source hierarchy. > > Signed-off-by:

Re: [PATCH] Documentation: spufs: correct a duplicate word typo

Randy Dunlap writes: > Fix a typo of "or" which should be "of". > > Signed-off-by: Randy Dunlap > Cc: Jeremy Kerr > Cc: Arnd Bergmann > Cc: linuxppc-dev@lists.ozlabs.org > Cc: Jonathan Corbet > --- > Documentation/filesystems/spufs/spufs.rst

Re: [PATCH 2/3] Documentation: use different label names for each arch's elf_hwcaps.rst

Bagas Sanjaya writes: > Sphinx reported duplicate label warning: > > WARNING: duplicate label elf_hwcaps_index, other instance in > Documentation/arm64/elf_hwcaps.rst > > The warning is caused by elf_hwcaps_index label name is already used for > arm64 documentation, whileas powerpc use the same

Re: linux-next: build warning after merge of the powerpc tree

"Aneesh Kumar K.V" writes: > Thanks for looking into this. I guess we also need to format the below table? > > | 08 40 > --| > | > 0 | 10 20 80 > | > 8 | 20 10 160 > | > 40| 80 160 10 > > > I don't know how to represent that in the documentation file. A table

Re: linux-next: build warning after merge of the powerpc tree

Stephen Rothwell writes: > Hi all, > > [cc'ing Jon in case he can fix the sphix hang - or knows anything about it] That's new to me. Which version of sphinx? jon

Re: [PATCH] docs: kernel-parameters: mark numa=off is supported by a bundle of architectures

Barry Song writes: > risc-v and arm64 support numa=off by common arch_numa_init() > in drivers/base/arch_numa.c. x86, ppc, mips, sparc support it > by arch-level early_param. > numa=off is widely used in linux distributions. it is better > to document it. > > Signed-off-by: Barry Song > --- >

Re: [PATCH] docs: powerpc: Fix misspellings and grammar errors

He Ying writes: > Reported-by: Hulk Robot > Signed-off-by: He Ying > --- > Documentation/powerpc/booting.rst| 2 +- > Documentation/powerpc/dawr-power9.rst| 2 +- > Documentation/powerpc/eeh-pci-error-recovery.rst | 2 +- > Documentation/powerpc/elfnote.rst

Re: [PATCH] docs: powerpc: Fix a typo

Bhaskar Chowdhury writes: > s/struture/structure/ > > Signed-off-by: Bhaskar Chowdhury > --- > Documentation/powerpc/firmware-assisted-dump.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/powerpc/firmware-assisted-dump.rst >

Re: [PATCH] docs: powerpc: Fix tables in syscall64-abi.rst

Andrew Donnellan writes: > Commit 209b44c804c ("docs: powerpc: syscall64-abi.rst: fix a malformed > table") attempted to fix the formatting of tables in syscall64-abi.rst, but > inadvertently changed some register names. > > Redo the tables with the correct register names, and while we're here,

Re: [PATCH 0/6] Add documentation for Documentation/features at the built docs

On Mon, 30 Nov 2020 16:36:29 +0100 Mauro Carvalho Chehab wrote: > This series got already submitted last year: > > > https://lore.kernel.org/lkml/cover.1561222784.git.mchehab+sams...@kernel.org/ > > Yet, on that time, there were too many other patches related to ReST > conversion floating

Re: [PATCH V2] Doc: admin-guide: Add entry for kvm_cma_resv_ratio kernel param

ode PowerPC KVM guests. > > Cc: linux-ker...@vger.kernel.org > Cc: kvm-...@vger.kernel.org > Cc: linuxppc-dev@lists.ozlabs.org > Cc: Paul Mackerras > Cc: Michael Ellerman > Cc: Jonathan Corbet > Reviewed-by: Randy Dunlap > Signed-off-by: Satheesh Rajendran > --- >

Re: [PATCH 00/20] Documentation: eliminate duplicated words

On Tue, 7 Jul 2020 11:03:54 -0700 Randy Dunlap wrote: > Documentation/admin-guide/mm/numaperf.rst |2 +- > Documentation/block/pr.rst|2 +- > Documentation/core-api/printk-basics.rst |2 +- > Documentation/dev-tools/kgdb.rst

Re: [PATCH v2 00/15] Documentation fixes

On Tue, 23 Jun 2020 09:08:56 +0200 Mauro Carvalho Chehab wrote: > As requested, this is a rebase of a previous series posted on Jan, 15. > > Since then, several patches got merged via other trees or became > obsolete. There were also 2 patches before that fits better at the > ReST conversion

Re: [PATCH 00/22] ReST conversion patches (final?)

On Mon, 15 Jun 2020 08:50:05 +0200 Mauro Carvalho Chehab wrote: > That's my final(*) series of conversion patches from .txt to ReST. > > (*) Well, running the script I'm using to check, I noticed a couple of new > *.txt files. > If I have some time, I'll try to address those last pending

Re: [PATCH v3 00/29] Convert files to ReST - part 2

On Tue, 28 Apr 2020 13:01:28 -0600 Jonathan Corbet wrote: > So I'm happy to merge this set, but there is one thing that worries me a > bit... > > > fs/cachefiles/Kconfig |4 +- > > fs/coda/Kconfig |2 +- >

Re: [PATCH v3 00/29] Convert files to ReST - part 2

On Mon, 27 Apr 2020 23:16:52 +0200 Mauro Carvalho Chehab wrote: > This is the second part of a series I wrote sometime ago where I manually > convert lots of files to be properly parsed by Sphinx as ReST files. > > As it touches on lot of stuff, this series is based on today's linux-next, > at

Re: [PATCH v2 00/33] Documentation fixes for Kernel 5.8

On Tue, 14 Apr 2020 18:48:26 +0200 Mauro Carvalho Chehab wrote: > Patches 1 to 5 contain changes to the documentation toolset: > > - The first 3 patches help to reduce a lot the number of reported > kernel-doc issues, by making the tool more smart. > > - Patches 4 and 5 are meant to

Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs

On Fri, 20 Mar 2020 16:11:01 +0100 Mauro Carvalho Chehab wrote: > This small series address a regression caused by a new patch at > docs-next (and at linux-next). I don't know how I missed that mess, sorry. I plead distracting times or something like that. Heck, I think I'll blame everything

Re: [patch V2 08/15] Documentation: Add lock ordering and nesting documentation

On Wed, 18 Mar 2020 21:43:10 +0100 Thomas Gleixner wrote: > From: Thomas Gleixner > > The kernel provides a variety of locking primitives. The nesting of these > lock types and the implications of them on RT enabled kernels is nowhere > documented. > > Add initial documentation. ...time to

Re: [PATCH v9 10/25] mm/gup: introduce pin_user_pages*() and FOLL_PIN

On Tue, 10 Dec 2019 18:53:03 -0800 John Hubbard wrote: > Introduce pin_user_pages*() variations of get_user_pages*() calls, > and also pin_longterm_pages*() variations. Just a couple of nits on the documentation patch > +++ b/Documentation/core-api/pin_user_pages.rst > @@ -0,0 +1,232 @@ > +..

Re: [PATCH 01/12] Documentation: move architectures together

On Fri, 12 Jul 2019 10:20:07 +0800 Alex Shi wrote: > There are many different archs in Documentation/ dir, it's better to > move them together in 'Documentation/arch' which follows from kernel source. So this seems certain to collide badly with Mauro's RST-conversion monster patch set. More to

Re: [RESEND PATCH] Documentation/stackprotector: powerpc supports stack protector

rch support documentation to reflect the same. > > Cc: Jonathan Corbet > Cc: Michael Ellerman > Cc: linux-...@vger.kernel.org > Cc: linux-ker...@vger.kernel.org > Cc: linuxppc-dev@lists.ozlabs.org > Signed-off-by: Bhupesh Sharma > --- > Resend, this time Cc'ing Jonathan and doc-list. Applied, thanks. jon

Re: [PATCH v4 19/28] docs: powerpc: convert docs to ReST and rename to *.rst

On Wed, 12 Jun 2019 14:52:55 -0300 Mauro Carvalho Chehab wrote: > Convert docs to ReST and add them to the arch-specific > book. > > The conversion here was trivial, as almost every file there > was already using an elegant format close to ReST standard. > > The changes were mostly to mark

Re: [PATCH] Documentation/stackprotector: powerpc supports stack protector

On Thu, 30 May 2019 18:37:46 +0530 Bhupesh Sharma wrote: > > This should probably go via the documentation tree? > > > > Acked-by: Michael Ellerman > > Thanks for the review Michael. > I am ok with this going through the documentation tree as well. Works for me too, but I don't seem to find

Re: [PATCH] Documentation: Add ARM64 to kernel-parameters.rst

On Fri, 3 May 2019 13:39:40 +0100 Will Deacon wrote: > > It looks like nobody has picked this up...so I've applied it. > > It's queued and tagged in the arm64 tree, which should also be in next! Just looked again, I still don't see it there. Josh's mitigations= change is there, but not this

Re: [PATCH] Documentation: Add ARM64 to kernel-parameters.rst

On Fri, 12 Apr 2019 22:56:21 -0500 Josh Poimboeuf wrote: > Add ARM64 to the legend of architectures. It's already used in several > places in kernel-parameters.txt. > > Suggested-by: Randy Dunlap > Signed-off-by: Josh Poimboeuf It looks like nobody has picked this up...so I've applied it.

Re: [PATCH v4 00/63] Include linux ACPI/PCI/X86 docs into Sphinx TOC tree

On Wed, 24 Apr 2019 00:28:29 +0800 Changbin Du wrote: > The kernel now uses Sphinx to generate intelligent and beautiful documentation > from reStructuredText files. I converted all of the Linux ACPI/PCI/X86 docs to > reST format in this serias. > > In this version I combined ACPI and PCI docs,

Re: Avoiding merge conflicts while adding new docs - Was: Re: [PATCH 00/57] Convert files to ReST

On Thu, 18 Apr 2019 09:42:23 -0300 Mauro Carvalho Chehab wrote: > After thinking a little bit and doing some tests, I think a good solution > would be to add ":orphan:" markup to the new .rst files that were not > added yet into the main body (e. g. something like the enclosed example).

Re: [PATCH v2 00/21] Convert hwmon documentation to ReST

On Fri, 12 Apr 2019 20:09:16 -0700 Guenter Roeck wrote: > The big real-world question is: Is the series good enough for you to accept, > or do you expect some level of user/kernel separation ? I guess it can go in; it's forward progress, even if it doesn't make the improvements I would like to

Re: [PATCH v2 00/21] Convert hwmon documentation to ReST

On Thu, 11 Apr 2019 14:07:31 -0700 Guenter Roeck wrote: > > While nobody does such split, IMHO, the best would be to keep the > > information outside Documentation/admin-guide. But hey! You're > > the Doc maintainer. If you prefer to move, I'm perfectly fine > > with that. > > > > Same here,

Re: [PATCH v2 00/21] Convert hwmon documentation to ReST

On Wed, 10 Apr 2019 16:22:37 -0300 Mauro Carvalho Chehab wrote: > This series converts the contents of Documentation/hwmon to ReST > format. > > PS.: I opted to group the conversion files per groups of maintainer > set, as, if I were to generate one patch per file, it would give around > 160

Re: [PATCH 0/1] Start conversion of PowerPC docs

On Fri, 08 Feb 2019 14:40:28 +1100 Michael Ellerman wrote: > > - I don't think this should be a top-level directory full of docs; the top > > level is already rather overpopulated. At worst, we should create an > > arch/ directory for architecture-specific docs. > > We currently have

Re: [PATCH 0/1] Start conversion of PowerPC docs

On Thu, 7 Feb 2019 17:03:15 +1100 "Tobin C. Harding" wrote: > As discussed at LCA here is the start to the docs conversion for PowerPC > to RST. > > This applies cleanly on top of the mainline (5.20-rc5) and Jon's tree > (docs-next branch). > > I'm guessing it should go in through the PowerPC

Re: [PATCH] Documentation: fix spelling mistake, EACCESS -> EACCES

On Fri, 26 Oct 2018 18:25:49 +0100 Colin King wrote: > Trivial fix to a spelling mistake of the error access name EACCESS, > rename to EACCES > > Signed-off-by: Colin Ian King > --- > Documentation/filesystems/spufs.txt | 2 +- > Documentation/gpu/drm-uapi.rst | 4 ++-- > 2 files

Re: [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/

On Tue, 4 Sep 2018 00:15:23 +0200 Henrik Austad wrote: > I don't really have an opinion to whether or not we /should/ have 00-INDEX, > but the above 00-INDEX should either be removed or be kept up to date. If > we should keep the files, I can try to keep them updated, but I rather not > if we

Re: [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/

On Tue, 4 Sep 2018 09:59:08 -0400 Steven Rostedt wrote: > On Tue, 4 Sep 2018 13:30:30 +0200 > Pavel Machek wrote: > > > I'd say this is still quite valueable, and it might be worth fixing, > > rather then removing completely. > > I agree. Perhaps we should have a 00-DESCRIPTION file in each

Re: [PATCH] Documentation: Add powerpc options for spec_store_bypass_disable

On Tue, 10 Jul 2018 12:08:36 +1000 Michael Ellerman wrote: > Document the support for spec_store_bypass_disable that was added for > powerpc in commit a048a07d7f45 ("powerpc/64s: Add support for a store > forwarding barrier at kernel entry/exit"). > > Signed-off-by: Michael Ellerman Applied,

Re: [PATCH 0/9] Fix references for some missing documentation files

On Tue, 26 Jun 2018 06:49:02 -0300 Mauro Carvalho Chehab wrote: > Having nothing to do while waiting for my plane to arrive while > returning back from Japan, I ended by writing a small series of > patches meant to reduce the number of bad Documentation/* > links that are detected by: >

Re: [PATCH 00/32] docs/vm: convert to ReST format

On Sun, 15 Apr 2018 20:36:56 +0300 Mike Rapoport wrote: > I didn't mean we should keep it as unorganized jumble of stuff and I agree > that splitting the documentation by audience is better because developers > are already know how to find it :) > > I just thought that

Re: [PATCH 00/32] docs/vm: convert to ReST format

Sorry for the silence, I'm pedaling as fast as I can, honest... On Sun, 1 Apr 2018 09:38:58 +0300 Mike Rapoport wrote: > My thinking was to start with mechanical RST conversion and then to start > working on the contents and ordering of the documentation. Some of the >

Re: [PATCH 00/32] docs/vm: convert to ReST format

On Wed, 21 Mar 2018 21:22:16 +0200 Mike Rapoport wrote: > These patches convert files in Documentation/vm to ReST format, add an > initial index and link it to the top level documentation. > > There are no contents changes in the documentation, except few spelling >

Re: [PATCH][DOC] ppc/idle: Add documentation for powersave=off

On Fri, 2 Dec 2016 00:08:26 +1100 Balbir Singh wrote: > Update kernel-parameters.txt to add Documentation > for powersave=off. Applied to docs-next, thanks. jon

Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it

On Thu, 9 Jul 2015 14:46:35 -0400 Eric B Munson emun...@akamai.com wrote: One other question...if I call mlock2(MLOCK_ONFAULT) on a range that already has resident pages, I believe that those pages will not be locked until they are reclaimed and faulted back in again, right? I suspect that

Re: [PATCH] Doc: powerpc: Fix typos in Documentation/powerpc

On Mon, 6 Jul 2015 23:41:57 +0900 Masanari Iida standby2...@gmail.com wrote: This patch fix some spelling typo found in Documentation/powerpc. Applied (with Ian's ack) to the docs tree, thanks. jon ___ Linuxppc-dev mailing list

Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it

On Tue, 7 Jul 2015 13:03:41 -0400 Eric B Munson emun...@akamai.com wrote: This patch introduces the ability to request that pages are not pre-faulted, but are placed on the unevictable LRU when they are finally faulted in. This can be done area at a time via the mlock2(MLOCK_ONFAULT) or the

Re: [PATCH V3 3/5] mm: mlock: Introduce VM_LOCKONFAULT and add mlock flags to enable it

On Wed, 8 Jul 2015 16:34:56 -0400 Eric B Munson emun...@akamai.com wrote: Quick, possibly dumb question: I've been beating my head against these for a little bit, and I can't figure out what's supposed to happen in this case: mlock2(addr, len, MLOCK_ONFAULT); munlock2(addr,

Re: [PATCH linux-next] Documentation: Build mic/mpssd only for x86_64

On Thu, 4 Dec 2014 13:27:29 -0800 Ashutosh Dixit ashutosh.di...@intel.com wrote: mic/mpssd along with MIC drivers are currently only usable on x86_64. So build mic/mpssd only for x86_64 to avoid build breaks on big-endian systems. I can certainly apply this. But it seems to me that this